NTN Rel-19

 RAN1#116

9.11   Non-Terrestrial Networks (NTN) for NR Phase 3 and Internet of Things (IoT) Phase 3

Please refer to RP-234078 for detailed scope of the WI for NR-NTN Phase 3. Please refer to RP-234077 for detailed scope of the WI for IoT-NTN Phase 3.

R1-2401769         Session notes for 9.11 (Non-Terrestrial Networks for NR Phase 3 and Internet of Things Phase 3)    Ad-Hoc Chair (Huawei)

Friday decision: The session notes are endorsed and contents reflected below.

[116-R19-NTN] – Mohamed (Thales)

Email discussion on Rel-19 NES enhancement

-        To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2400843         Work plan for NR_NTN_Ph3        THALES

Further revised in R1-2401730.

R1-2401298         Work Plan for Rel-19 IoT NTN    MediaTek Inc.

9.11.1    NR-NTN downlink coverage enhancement

R1-2401470         An operator view on Downlink Coverage Enhancements for FR2-NTN            Eutelsat Group  (rev of R1-2400897           )

·       Time domain power saving techniques and flexible resource allocation should be studied; techniques studied in the context of TN should also be considered where applicable to NTN.

·       RAN1 shall consider Downlink Coverage Enhancements from a system level point of view, taking into account the differences between FR2-NTN and FR1-NTN.

Decision: The document is noted.

R1-2400132         Discussion on downlink coverage enhancements for NR NTN              Huawei, HiSilicon

·       The percentage of served beam footprints, where UEs can access the NTN network, needs to be improved for NTN system level coverage enhancement.

·       The unequal distribution of user density among different beam footprints should be considered in the system level coverage enhancement, e.g. initial access enhancement.

·       The longer period for transmission of common signal/channel, e.g., SSB and SIBs is to be discussed to support Rel-19 system level coverage enhancement.

·       The Tx power per active beam for link level coverage evaluation should be determined based on the satellite total transmission power and the number of active beams, rather than simply reduced by 6 or 9dB.

·       The link level coverage enhancement solutions by prolonging the transmission duration for DL energy accumulation at UE side are not to be discussed in Rel-19 considering it cannot resolve the power limitation issue due to the power sharing among active beams.

·       Multiple simultaneous active beams should be considered in the additional reference satellite payload parameters.

·       The maximum Tx power constraint on satellite payload is to be considered in the additional reference satellite parameters for Rel-19 NTN.

·       The active beam number and Tx power constraint are determined considering the commercial satellite capability.

·       The phased array antenna is modelled in the additional reference satellite parameters for Rel-19 NTN.

·       The phased array model defined in TR38.901 can be considered as a starting point for the phase-arrayed antenna model for Rel-19 NTN additional reference satellite payload parameters.

·       Adopt the following phased array antenna parameters for LEO as baseline.

·       The number of active beams is assumed as 16 as a baseline for Rel-19 NTN coverage enhancement.

·       Total Tx power for a satellite is assume to be 200W~300W as a baseline for Rel-19 NTN..

·       The same methodology in Rel-18 coverage enhancement can be reused with the consideration of reasonable power constraints on satellites, including the maximum total satellite power and the number of simultaneous active beams.

·       Consider a single satellite with multiple beam footprints as the evaluation methodology for system level coverage enhancement, with the detailed parameters in Table7:

·       RAN1 to consider the following metrics in Table 8 in the system level coverage enhancement evaluation:

Decision: The document is noted.

R1-2400071         Discussion on NR-NTN downlink coverage enhancement              Spreadtrum Communications

R1-2400259         Discussion on NR-NTN downlink coverage enhancement              vivo

R1-2400303         Discussion on NR NTN Downlink coverage enhancements              THALES

R1-2400344         Discussion on NR-NTN DL coverage enhancement    CMCC

R1-2400355         Discussion on DL coverage enhancement for NR NTN              ZTE

R1-2400402         Downlink Coverage Enhancement for NR NTN          Google

R1-2400424         Discussion on downlink coverage enhancement for NR NTN              CATT

R1-2400478         NR-NTN downlink coverage enhancement   NEC

R1-2400499         NR-NTN downlink coverage enhancement   Fraunhofer IIS, Fraunhofer HHI

R1-2400516         Seamless NTN downlink coverage for high-availability services              Dell Technologies

R1-2400528         Discussion on NR-NTN downlink coverage enhancement              Honor

R1-2400549         Discussion on NR-NTN downlink coverage enhancement              xiaomi

R1-2400576         NR-NTN downlink coverage enhancement   InterDigital, Inc.

R1-2400602         Discussion on NR-NTN downlink coverage enhancement              OPPO

R1-2400749         Discussion on downlink coverage enhancement for NR-NTN              Samsung

R1-2400787         Discussion on NR-NTN downlink coverage enhancement        LG Electronics

R1-2400837         Discussion on downlink coverage enhancements for NR NTN              CCU, NTPU

R1-2400871         NR-NTN Downlink Coverage Enhancement PANASONIC

R1-2400875         Discussion on downlink coverage enhancement for NR NTN              Lenovo

R1-2400971         Downlink coverage enhancements for NR over NTN  Nokia, Nokia Shanghai Bell

R1-2401029         Study on NR-NTN Downlink Coverage Enhancement              Apple

R1-2401059         Beam groups/patterns for NR-NTN downlink coverage enhancement       Sharp

R1-2401079         Discussion on DL coverage enhancements for NR-NTN              NICT

R1-2401592         Discussion on downlink coverage enhancement for NR NTN              Baicells (rev of R1-2401083)

R1-2401130         Discussion on DL coverage enhancement for NR-NTN              NTT DOCOMO, INC.

R1-2401237         Discussion on NR-NTN downlink coverage enhancement              ETRI

R1-2401282         Link Level Enhancements for DL Coverage of NR NTN              CEWiT

R1-2401299         Discussion on NR-NTN downlink coverage enhancement              MediaTek Inc.

R1-2401342         On NR-NTN downlink coverage enhancement           Ericsson

R1-2401458         Downlink coverage enhancement for NR NTN            Qualcomm Incorporated

R1-2401843         FL Summary #1: NR-NTN downlink coverage enhancements              Moderator (THALES)

R1-2401844         FL Summary #2: NR-NTN downlink coverage enhancements              Moderator (THALES)

From Friday session

Agreement

For DL coverage study, consider the following additional reference satellite parameters scenarios for LEO600km Set1 in FR1 (i.e., S-band), referred to as Set1-1 FR1, Set1-2 FR1 and Set1-3 FR1:

Note: RAN1 will aim to identify necessary enhancements for these scenarios in the study phase. At the end of the study phase, RAN1 will further discuss whether the potential enhancements will be specified within Rel-19 framework.

Agreement

For DL coverage study at system level, consider the following additional reference satellite payload parameters for LEO600km in FR2 (i.e., Ka-band):

Agreement

·       Adopt the following phased array antenna parameters for LEO 600km in FR1:

Agreement

RAN1 to consider the following performance metrics for DL Coverage enhancement evaluation at system level:

At least:

• CDF of the received SINR
• The dwell time and revisit time interval for each beam illumination across the coverage
• Periodicity of common control channels (e.g. SSB, CORESET0/SIB1, SIB19) and corresponding coverage ratio

Other metrics may be reported such as

• CDF of the cell throughput
• CDF of user perceived throughput (UPT)
• CDF of Latency
• Ratio of mean served cell throughput and offered cell throughput, denoted by 𝜌 (refer to TR36.889)

For system level study based on analytical evaluation:

• N1 beam footprints are in state “off”
• These beam footprints are not served by any signal (no satellite service in this area)
• N2 beam footprints are in state “common messages only”
• These beam footprints do not have any active user traffic, and are served the necessary information for cell discovery and initial access.
• Optionally, companies may consider user arrival (e.g. RACH access) in this type of cell, and should describe how this is taken into account in the analytical evaluation
• N3 beam footprints are in state “active traffic”
• These beam footprints have X active (e.g. VoNR) users each.
• These beam footprints are also served the necessary information for cell discovery and initial access
• N1 + N2 + N3 = “Total number of beam footprints “
• N1, N2, N3, X are to be reported by companies.
• Resource utilization obtained under the assumptions above is to be reported by companies.
• Other assumptions made in the evaluation are to be reported by companies, e.g. power sharing scheme, beam hopping scheme, etc.

Agreement

For NR NTN Rel-19 DL coverage evaluation, UE characteristics for handheld terminals in Table 6.1.1.1-3 in TR 38.821 can be reused, with the following:

• -5.5 dBi antenna gain is assumed
• at least 2Rx are considered at the UE
• 4Rx can be optionally considered and reported

Note: Redcap device is not considered in the scope of DL coverage study.

Agreement

The following traffic models are considered for system level evaluation of DL coverage:

• FTP3: as in Table 6.1.1.1-7 of TR 38.821: 0.5MB as packet size, 200ms as mean inter-arrival time
• FTP3 IM: 0.1MB as packet size, 2s as mean inter-arrival time
• VoIP can be considered in the evaluation.

It is up to company report which traffic model is used among the discussed traffic models in their evaluations.

·       Other models may be used as well, and parameter (e.g. packet size and arrival rate) adjustment can be optionally considered and reported.

Agreement

For NR NTN Rel-19 DL coverage evaluation, Beam layout defined in Table 6.1.1.1-4 in TR 38.821 can be reused.

·       Using other beam layouts is not precluded, and should be reported by companies.

Agreement

For NR NTN Rel-19 DL coverage evaluation, a value of beam steering latency equal to 0 at least if phase array antenna is assumed.

Values different from 0 can be optionally reported.

Agreement

DL coverage is evaluated at link level with the following considerations:

• NGSO at LEO-600 operating in FR1 is considered in priority
• Additional satellite payload parameters defined for system level evaluation are used
• FFS: Antenna gain reduction due to steering loss can be considered

Agreement

For the evaluation of NTN downlink coverage at link level, reuse the target data rate from Rel-18 NTN Coverage enhancements:

• For VoIP: AMR 4.75 kbps (TBS of 184 bits without CRC in physical layer) with 20 ms data arriving interval
• For data rate service: both 3 kbps and 1Mbps can be considered
• Companies can also use the data rates corresponding to the traffic types used for system level evaluations

Agreement

For link-level study, downlink coverage performance in NR NTN is evaluated according to the following steps.

·       Step 1: CNR is calculated as defined in 6.1.3.1 of TR 38.821

·       Step 2: Required SNR of target service is evaluated by LLS

·       Step 3: The CNR and the required SNR are compared

Agreement

For link-level study, for NR NTN DL coverage enhancement, the following channels/signals can be considered for evaluations:

• PDSCH for VoIP
• PDSCH for low data rate service
• PDSCH Msg.2
• PDSCH Msg.4
• PDSCH carry SIB, e.g., SIB1, SIB 19
• PDSCH for paging
• PDCCH
• Broadcast PDCCH (e.g. PDCCH of Msg.2, paging)
• SSB

Note: RAN1 will aim to identify necessary link-level enhancements for these channels in the study phase. At the end of the study phase, RAN1 will further discuss whether the potential link-level enhancements will be specified within Rel-19 framework.

Agreement

For DL coverage performance evaluation, the following are assumed for all channels/signals

• Channel model/Delay spread:
• Channel model as in Table 6.1.2-4 of TR38.821, NTN-TDL-C (LOS)
• Evaluation scenario:
• Rural (LOS)
• Channel estimation: Realistic estimation:
• Companies are encouraged to report channel estimation method.
• SCS:
• 15 kHz only
• UE speed: 3 km/h
• Frequency drift: TBD
• Frequency offset: 0.1 ppm

Agreement

For link budget calculation, parameters in the following table are assumed:

R1-2401845         FL Summary #3: NR-NTN downlink coverage enhancements              Moderator (THALES)

9.11.2    Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands

Work in RAN1 is limited to checking whether any essential changes are needed for their support (i.e. focusing on HD collision rules) by end of Q2/2024.

R1-2401459         Support of Redcap and eRedcap UEs in NR NTN   Qualcomm Incorporated

·       Support the configuration of the whole or a subset of SIB19 SI windows during which a HD-FDD UE may drop a UL transmission if it collides with PDSCH carrying SIB19 or the associated scheduling PDCCH.

o   During the above configured SIB19 SI windows, it’s up to UE to follow the existing collision rules or prioritize the reception of SIB19.

o   FFS signaling of the configuration.

·       For HD-FDD UEs in NR NTN, UE cancels the UL transmission or drops the DL reception for the collisions defined as error cases in Rel-18.

o   Support network configuration of dropping DL reception or cancelling UL transmission.

·       For PUSCH repetition and TBoMS for HD-FDD UEs in RRC-Connected in NR NTN, UL symbols overlapping with the duration from SSB_start-T_TX-_RXT_C+TA_min to SSB_end+T_RX-TX T_C+TA_max  are invalid resource where SSB_start and SSB_end are the start and the end time of the UL symbols that have the same index of the SSB start and end symbols, respectively.

o   For Type A PUSCH repetition and when AvailableSlotCounting is enabled and for PUSCH TBoMS, a slot that has at least one invalid symbol is not counted.

o   FFS Signaling of TA_max and TA_min

·       For HD-FDD UEs in NR NTN, support a new UE specific TA report with the granularity of the duration of a UL symbol. 

·       For HD-FDD UEs in NR NTN, support UE report of TA drifting rate together with the enhanced UE specific TA report.

Decision: The document is noted.

R1-2400072         Discussion on support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands Spreadtrum Communications

R1-2400133         Discussion on HD-FDD RedCap UEs and eRedCap UEs for FR1-NTN      Huawei, HiSilicon

R1-2400260         Discussion on support of RedCap and eRedCap UEs with NR-NTN      vivo

R1-2400345         Discussion on the collision issues of HD-FDD Redcap UE in FR1-NTN             CMCC

R1-2400356         Discussion on support of RedCap/eRedCap UEs for NR NTN              ZTE

R1-2400425         Discussion on the operation of RedCap and eRedCap UEs In NTN              CATT

R1-2400550         Discussion on the support of Redcap UE for NTN operating on FR1 bands            xiaomi

R1-2400603         Discussion on supporting of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands OPPO

R1-2400627         Discussion on half-duplex RedCap issues for NTN FR1 operation              InterDigital, Inc.

R1-2400750         Discussion on support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands Samsung

R1-2400788         Discussion on support of (e)RedCap UEs with NR-NTN operating in FR1-NTN bands            LG Electronics

R1-2400972         RedCap support for NR over NTN while operating in FR1-NTN bands     Nokia, Nokia Shanghai Bell

R1-2401030         Discussion on support of RedCap UEs with NR NTN operation              Apple

R1-2401131         Discussion on support of RedCap and eRedCap UEs in FR1-NTN              NTT DOCOMO, INC.

R1-2401194         On HD-FDD Redcap UEs for NTN Ericsson

R1-2401238         Discussion on HD UEs with NR NTN           ETRI

R1-2401300         Discussion on support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands MediaTek Inc.

R1-2401847         Summary for 9.11.2         Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands   Moderator (CATT)

From Friday session

Agreement

Study at least the following scenarios for (e)RedCap HD-FDD UEs for NTN:

·       Whether existing handling rules for the following cases should be reused or updated when taking into account TA mismatch between actual TA used by UE and assumed TA at the gNB based on available TA report:

o   Case 1: Dynamically scheduled DL reception collides with semi-statically configured UL transmission

o   Case 2: Semi-statically configured DL reception collides with dynamically scheduled UL transmission

o   Case 3: Semi-statically configured DL reception collides with semi-statically configured UL transmission 

o   Case 4: Dynamically scheduled DL reception collides with dynamic scheduled UL transmission

o   Case 5: Configured SSB collides with dynamically scheduled or configured UL transmission

o   Case 6: Dynamic or semi-static DL collides with valid RO

o   Case 7: Collision due to direction switching

·       At least the following potential issues can be further considered for (e)RedCap HD-FDD UEs

o   Error cases in case 3 and case 4

o   SIB19 reception collides with UL transmission

o   Slot counting for UL repetition transmission colliding with SSB reception

o   Invalid symbol determination for PUSCH repetition type B

o   Actual TDW determination due to the collision between DL reception and UL transmission with DMRS bundling

o   CPU occupation due to omitted DL reception or UL transmission

Note: Both GSO and Non-GSO should be considered.

Final summary in R1-2401861.

9.11.3    NR-NTN uplink capacity/throughput enhancement

R1-2400973         On NR-NTN uplink capacity/throughput enhancements              Nokia, Nokia Shanghai Bell

·       The feature of OCC need to be evaluated thoroughly in terms of robustness and efficiency prior to determining to specify it.

·       Assess the performance impact of OCC-enabled PUSCH in comparison to PUSCH without OCC through link-level simulations. The evaluation involves the following steps:

o   Step 1: Evaluate the single UE performance without OCC-enabled PUSCH and determine SNR for BLER at 10%

o   Step 2: Evaluate BLER performance for OCC enabled PUSCH where there are other OCC-enabled PUSCH transmissions overlapping but with different OCC. The evaluation is performed within the determined SNR range for single UE PUSCH.

o   Step 3. Determine SNR gap at 10% BLER between the single UE PUSCH and OCC enabled PUSCH to identify any potential performance degradation.

·       Incorporate the simulation assumptions outlined in Table 1 as the basis for conducting performance evaluations.

·       The feature of OCC is considered only for cases with PUSCH repetitions configured.

·       The length of the OCC being applied should match the number of repetitions used for PUSCH transmissions.

·       RAN1 to investigate and assess the maximum number of UEs that can be supported by OCC.

·       Examine and explore the benefits and challenges associated with various OCC spreading schemes.

·       If adopted, the feature of OCC should focus on mechanisms that are simple to implement and that ensure that multiple UEs would support the feature.

Decision: The document is noted.

R1-2400073         Discussion on NR-NTN uplink capacity/throughput enhancement              Spreadtrum Communications

R1-2400134         Discussion on uplink capacity/throughput enhancement for FR1-NTN      Huawei, HiSilicon

R1-2400261         Discussion on NR-NTN uplink capacity enhancement              vivo

R1-2400346         Discussion on the NR-NTN uplink capacity/throughput enhancements      CMCC

R1-2400357         Discussion on UL capacity enhancement for NR NTN              ZTE

R1-2400403         Uplink Capacity Enhancement for NR NTN  Google

R1-2400426         Discussion on UL capacity enhancement for NR NTN              CATT

R1-2400479         NR-NTN uplink capacity/throughput enhancement    NEC

R1-2400517         Disaggregated NTN uplink and downlink sessions      Dell Technologies

R1-2400551         Discussion on NR-NTN PUSCH capacity enhancement              xiaomi

R1-2400604         Discussion on NR-NTN uplink capacity/throughput enhancement              OPPO

R1-2400628         NR-NTN uplink capacity/throughput enhancement    InterDigital, Inc.

R1-2400674         Discussion on NR-NTN uplink enhancement              China Telecom

R1-2400751         Discussion on uplink capacity/throughput enhancement for NR-NTN      Samsung

R1-2401484         Discussion on NR-NTN uplink capacity/throughput enhancement              LG Electronics    (rev of R1-2400789)

R1-2400819         Discussion on NR-NTN Uplink Capacity/Throughput Enhancement       Lenovo

R1-2400824         Uplink capacity/throughput enhancement for NR-NTN              Panasonic

R1-2400977         On uplink capacity/throughput enhancement for NR NTN              Ericsson

R1-2401031         Study on NR-NTN Uplink Capacity Enhancement      Apple

R1-2401080         NR-NTN uplink capacity/throughput enhancement    NICT

R1-2401132         Discussion on NR-NTN uplink capacity/throughput enhancement              NTT DOCOMO, INC.

R1-2401133         NR-NTN uplink capacity/throughput enhancement    Sharp

R1-2401239         Discussion on NR-NTN uplink capacity/throughput enhancement              ETRI

R1-2401301         Discussion on NR-NTN uplink capacity and throughput              MediaTek Inc.

R1-2401460         NR-NTN uplink capacity / throughput enhancement   Qualcomm Incorporated

R1-2401543         Feature lead summary #1 of AI 9.11.3 on NR-NTN uplink capacity and throughput Moderator (MediaTek)

From Wednesday session

Agreement

·       Adopt the table below for assumptions for Evaluation parameters for link level evaluation in NR NTN UL capacity and throughput enhancements

Agreement

·       Adopt the table below for assumptions for modelling impairments for link level evaluation in NR NTN UL capacity and throughput enhancements

Agreement

·       Adopt the table below for assumptions for KPIs for link level evaluation in NR NTN UL capacity and throughput enhancements

R1-2401791         Feature lead summary #2 of AI 9.11.3 on NR-NTN uplink capacity and throughput    Moderator (MediaTek)

9.11.44    IoT-NTN uplink capacity/throughput enhancement

R1-2400480         IoT-NTN uplink capacity/throughput enhancement              NEC

·       Support study multiplex NPRACH with OCC and legacy NPRACH  in uplink capacity enhancement for IoT-NTN.

·       Support study if the legacy PRACH partition mechanism for UEs with single/multi-tone Msg3 transmission capability can be reused for NPRACH with OCC and legacy NPRACH  in uplink capacity enhancement for IoT-NTN.

·       Support study if the anchor carrier and non-anchor carrier selection probability could be enhanced to multiplex NPRACH with OCC and legacy NPRACH  in uplink capacity enhancement for IoT-NTN.

·       Support study of the performance of NPRACH multiplexing transmission with different spreading modes (e.g. symbol-level, symbol group-level, repetition-level) in uplink capacity enhancement for IoT-NTN.

·       Support study of the performance of different frequency hopping mechanisms for NPRACH with OCC in uplink capacity enhancement for IoT-NTN.

·       Support study of the performance of different codebook index hopping mechanisms for NPRACH with OCC in uplink capacity enhancement for IoT-NTN.

·       Support study on whether the timing and frequency synchronizing should be enhanced to support NPRACH with OCC in uplink capacity enhancement for IoT-NTN.

·       Support study of the NPUSCH format 1 enhancement with OCC for IoT-NTN based on the outcome of the PUSCH enhancement with OCC for NR-NTN.

Decision: The document is noted.

R1-2400074         Discussion on IoT-NTN uplink capacity/throughput enhancement              Spreadtrum Communications

R1-2400135         Discussion on UL capacity enhancements for IoT NTN              Huawei, HiSilicon

R1-2400262         Discussion on IoT-NTN uplink capacity enhancement              vivo

R1-2400347         Discussion on the IoT -NTN uplink capacity/throughput enhancements      CMCC

R1-2400358         Discussion on UL capacity enhancement for IoT NTN              ZTE

R1-2400427         Discussion on UL capacity enhancement for IoT NTN              CATT

R1-2400552         Discussion on IoT-NTN uplink capacity enhancement              xiaomi

R1-2400605         Discussion on IoT-NTN uplink capacity/throughput enhancement              OPPO

R1-2400629         IoT-NTN uplink capacity/throughput enhancement    InterDigital, Inc.

R1-2400752         Discussion on uplink capacity/throughput enhancement for IoT-NTN      Samsung

R1-2400790         Discussion on IoT-NTN uplink capacity/throughput enhancement              LG Electronics

R1-2400876         Discussion on uplink capacity enhancement for IoT NTN              Lenovo

R1-2400879         IoT-NTN uplink capacity enhancement         Nokia, Nokia Shanghai Bell

R1-2401032         Discussion on IoT-NTN uplink capacity enhancement              Apple

R1-2401061         IoT NTN uplink enhancement with NPRACH multiplexing              Sharp

R1-2401195         On uplink capacity enhancements for IoT-NTN           Ericsson

R1-2401240         Discussion on IoT-NTN uplink capacity enhancement              ETRI

R1-2401302         Discussion on IoT-NTN uplink capacity and throughput              MediaTek Inc.

R1-2401373         IoT-NTN uplink capacity-throughput enhancement    Mavenir

R1-2401461         IOT-NTN uplink capacity/throughput enhancement   Qualcomm Incorporated

R1-2401607         FL Summary #1 for IoT-NTN       Moderator (Sony)

From Wednesday session

Agreement

For single-tone NPUSCH format 1 transmissions with both 3.75kHz and 15kHz SCS, the following OCC schemes are considered by RAN1 for further study:

• Time domain OCC where OCC spreads across:

• Symbol-level
• Slot-level
• Repetition-level
• RV-level

For multi-tone NPUSCH format 1 transmissions, the following OCC schemes are considered by RAN1 for further study:

• Time domain OCC where OCC spreads across:

• Symbol-level
• Slot-level (including Nslot level)
• Repetition-level
• RV-level

• Intra-symbol pre-DFT spreading OCC

Agreement

·       The following evaluation assumptions are used for the study of OCC for NPUSCH format 1:

 RAN1#116-bis

9.11   Non-Terrestrial Networks (NTN) for NR Phase 3 and Internet of Things (IoT) Phase 3

Please refer to RP-240775 for detailed scope of the WI for NR-NTN Phase 3. Please refer to RP-234077 for detailed scope of the WI for IoT-NTN Phase 3.

R1-2403666         Session notes for 9.11 (Non-Terrestrial Networks for NR Phase 3 and Internet of Things Phase 3)    Ad-Hoc Chair (Huawei)

Friday decision: The session notes are endorsed and contents reflected below.

[116bis-R19-NTN] – Mohamed (Thales)

Email discussion on Rel-19 NTN enhancement

-        To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2401990         Work plan for Rel-19 NR_NTN_Ph3             THALES

9.11.1    NR-NTN downlink coverage enhancement

R1-2401988         Discussion on NR NTN Downlink coverage enhancements              THALES

R1-2402003         Discussion on downlink coverage enhancements for NR NTN              Huawei, HiSilicon

R1-2402078         On NR-NTN downlink coverage enhancement           Ericsson

R1-2402120         Discussion on NR-NTN downlink coverage enhancement              Spreadtrum Communications

R1-2402173         NR-NTN downlink coverage enhancement   InterDigital, Inc.

R1-2402259         Discussion on NR-NTN downlink coverage enhancement              vivo

R1-2402286         Downlink Coverage Enhancement for NR NTN          Google

R1-2402343         Discussion on NR-NTN downlink coverage enhancement              OPPO

R1-2402372         Performance evaluation of downlink coverage enhancement for NR NTN              CATT

R1-2402483         Discussion on downlink coverage enhancement for NR-NTN              Samsung

R1-2402580         Discussion on NR-NTN DL coverage enhancement    CMCC

R1-2402589         Discussion on downlink coverage enhancement for NR NTN              Lenovo

R1-2402622         Discussion on DL coverage enhancement for NR NTN              ZTE

R1-2402655         Discussion on NR-NTN downlink coverage enhancement              Xiaomi

R1-2402752         Discussion on downlink coverage enhancement for NR NTN              Baicells

R1-2402772         NR-NTN downlink coverage enhancement   NEC

R1-2402811         Discussion on NR-NTN downlink coverage enhancement        LG Electronics

R1-2402902         On NR-NTN Downlink Coverage Enhancement         Apple

R1-2402916         NR-NTN downlink coverage enhancement with beam groups              Sharp

R1-2402934         Discussion on NR-NTN downlink coverage enhancement              MediaTek

R1-2403029         Discussion on NR-NTN downlink coverage enhancement              ETRI

R1-2403412         Downlink Coverage Enhancements for NR NTN        CEWiT              (rev of R1-2403067)

R1-2403080         Downlink coverage enhancements for NR over NTN  Nokia, Nokia Shanghai Bell

R1-2403139         Discussion on DL coverage enhancements for NR-NTN              NICT

R1-2403211         Downlink coverage enhancement for NR NTN            Qualcomm Incorporated

R1-2403258         Discussion on DL coverage enhancement for NR-NTN              NTT DOCOMO, INC.

R1-2403283         NR-NTN Downlink Coverage Enhancement Panasonic

R1-2403403         On the SAN phased-array antenna characteristics ESA

R1-2401991         FL Summary #1: NR-NTN downlink coverage enhancements              THALES

From Wednesday session

Agreement

For coverage evaluation of PDCCH in NR NTN, the following table is assumed:

Agreement

For coverage evaluation of PDSCH in NR NTN, the following table is assumed:

Agreement

Antenna gain reduction due to steering loss is not considered in the link level evaluation.

Note: This is aligned with the assumptions made in Rel-18 UL coverage enhancement.

Observation

The CNRs for the satellite payload parameters Set 1-1, Set 1-2 and Set 1-3 are equal to -1.9 dB, -1.9 dB and -9.9 dB respectively.

Agreement

Confirm the Satellite phased-array antenna parameters for LEO 600km in FR1 defined in RAN1#116.

Al least the above model is considered for SLS to ease the alignment between evaluation results. The model below can be optionally considered:

Note 1: The maximum antenna gain is determined by considering an overall array efficiency [of 50%.]

R1-2401992         FL Summary #2: NR-NTN downlink coverage enhancements              THALES

From Thursday session

Agreement

For coverage evaluation of PDSCH in NR NTN, the following payload sizes for PDSCH are assumed:

Note: At least the above values are simulated and reported. Other values can be considered.

Note: the values above are not the TBS.

Agreement

For DL coverage study at system level, it is up to companies to report the following parameters for LEO600km Set1-1 FR2:

Agreement

For coverage performance evaluation of DL channels/signals before the SIB19 acquisition, the maximum Doppler frequency drift is assumed to be equal to 0.27 ppm/s based on TR 38.821.

Final summary in R1-2401993.

9.11.2    Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands

Work in RAN1 is limited to checking whether any essential changes are needed for their support (i.e. focusing on HD collision rules) by end of Q2/2024.

R1-2402004         Discussion on HD-FDD RedCap UEs and eRedCap UEs for FR1-NTN      Huawei, HiSilicon

R1-2402121         Discussion on support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands Spreadtrum Communications

R1-2402174         Discussion on half-duplex RedCap issues for NTN FR1 operation              InterDigital, Inc.

R1-2402260         Discussion on support of RedCap and eRedCap UEs with NR-NTN      vivo

R1-2402344         Discussion on supporting of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands OPPO

R1-2402373         Discussion on the operation of RedCap and eRedCap UEs In NTN              CATT

R1-2402484         Discussion on support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands Samsung

R1-2402524         Discussion on Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands China Telecom

R1-2402581         Discussion on the collision issues of HD-FDD Redcap UE in FR1-NTN             CMCC

R1-2402623         Discussion on support of RedCap/eRedCap UEs for NR NTN              ZTE

R1-2402656         Discussion on the support of Redcap UE for NTN operating on FR1 bands            Xiaomi

R1-2402729         Discussion on support of RedCap/eRedCap UEs in NR NTN              Honor

R1-2402812         Discussion on support of (e)RedCap UEs with NR-NTN operating in FR1-NTN bands            LG Electronics

R1-2402903         On support of RedCap UEs with NR NTN operation  Apple

R1-2402935         Discussion on support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands MediaTek

R1-2403004         On HD-FDD Redcap UEs for NTN Ericsson

R1-2403030         Discussion on HD UEs with NR NTN           ETRI

R1-2403039         Discussion on HD-FDD RedCap UEs and eRedCap UEs for FR1-NTN      TCL

R1-2403081         Considerations for RedCap HD-FDD operation for NR over NTN              Nokia, Nokia Shanghai Bell

R1-2403161         Discussion on support of RedCap/eRedCap UEs in NTN              CAICT

R1-2403212         Support of Redcap and eRedcap UEs in NR NTN       Qualcomm Incorporated

R1-2403259         Discussion on support of RedCap and eRedCap UEs in FR1-NTN              NTT DOCOMO, INC.

R1-2403633         Summary #1 for Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands      Moderator (CATT)

Presented in Wednesday session

R1-2403743         Summary #2 for Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands      Moderator (CATT)

From Thursday session

Observation

To avoid the occurrence of error cases 3 and 4 through network scheduling, there are less resources available for a scheduled HD-FDD RedCap/eRedCap UE in NTN compared to TN when there is TA mismatch between actual TA used by the UE and assumed TA for the UE at the gNB.

Observation

For collision cases 1, 2, 5 and 6, when there is TA mismatch between actual TA used by the UE and assumed TA for the UE at the gNB, there might be less resources available for the scheduled HD-FDD RedCap/eRedCap UE in NTN compared to TN if gNB attempts to avoid the collision or there is a loss of DL/UL transmissions due to collision.

Observation

When there is TA mismatch between actual TA used by the UE and assumed TA for the UE at the gNB, there may be a BLER performance degradation for the reception of UL transmissions at the gNB for the scheduled HD-FDD RedCap/eRedCap UE in NTN compared to TN if gNB does not attempt to avoid the collision at least in the following cases:

·         UL transmission with repetitions due to different available slot counting at UE and gNB when colliding with SSB reception.

·         PUSCH repetition type B due to different invalid symbol determination at gNB and UE when colliding with DL transmissions.

·         UL transmission with DMRS bundling due to the different actual TDW determination at gNB and UE when colliding with DL transmissions.

Note: the above cases happen at least with one of collision cases 1, 2, 5, 6, and 7.

Final summary in R1-2403787.

9.11.3    NR-NTN uplink capacity/throughput enhancement

R1-2402005         Discussion on uplink capacity/throughput enhancement for FR1-NTN      Huawei, HiSilicon

R1-2402122         Discussion on NR-NTN uplink capacity/throughput enhancement              Spreadtrum Communications

R1-2402175         NR-NTN uplink capacity/throughput enhancement    InterDigital, Inc.

R1-2402261         Discussion on NR-NTN uplink capacity enhancement              vivo

R1-2402287         Uplink Capacity Enhancement for NR NTN  Google

R1-2402345         Discussion on NR-NTN uplink capacity/throughput enhancement              OPPO

R1-2402374         Discussion on UL capacity enhancement for NR NTN              CATT

R1-2402485         Discussion on uplink capacity/throughput enhancement for NR-NTN      Samsung

R1-2402525         Discussion on NR-NTN uplink enhancement              China Telecom

R1-2402534         Discussion on Uplink Capacity/Throughput Enhancement for NR-NTN      Langbo

R1-2402582         Discussion on the NR-NTN uplink capacity/throughput enhancements      CMCC

R1-2402594         On uplink capacity/throughput enhancement for NR NTN              Ericsson

R1-2402624         Discussion on UL capacity enhancement for NR NTN              ZTE

R1-2402657         Discussion on NR-NTN PUSCH capacity enhancement              Xiaomi

R1-2402773         NR-NTN uplink capacity/throughput enhancement    NEC

R1-2402813         Discussion on NR-NTN uplink capacity/throughput enhancement              LG Electronics

R1-2402904         On NR-NTN Uplink Capacity Enhancement Apple

R1-2402936         Discussion on NR-NTN uplink capacity and throughput              MediaTek

R1-2402995         Uplink capacity/throughput enhancement for NR-NTN              Panasonic

R1-2403031         Discussion on NR-NTN uplink capacity/throughput enhancement              ETRI

R1-2403040         Discussion on NR-NTN uplink capacity/throughput enhancement              TCL

R1-2403077         Discussion on uplink capacity/throughput enhancement for NR-NTN      Lenovo

R1-2403082         Uplink capacity enhancement considerations for NR over NTN              Nokia, Nokia Shanghai Bell

R1-2403140         Discussion on NR-NTN uplink capacity/throughput enhancement              NICT

R1-2403213         NR-NTN uplink capacity - throughput enhancement  Qualcomm Incorporated

R1-2403260         Discussion on NR-NTN uplink capacity/throughput enhancement              NTT DOCOMO, INC.

R1-2403402         Views on NR-NTN PUSCH capacity enhancement    Mitsubishi Electric RCE

R1-2403422         Feature lead summary #1 of AI 9.11.3 on NR-NTN uplink capacity and throughput Moderator (MediaTek)

From Tuesday session

Agreement

Support OCC for PUSCH in Rel-19 NR NTN:

• At least PUSCH with Type A repetition
• FFS PUSCH without Type A repetition for intra-symbol and/or inter-symbol cases
• At least code length 2 or 4, FFS code length 8
• FFS: number of RBs
• Potential OCC techniques listed below are for further down-selection:
• Inter-slot time-domain OCC with PUSCH repetition Type A
• Inter-symbol(s) time domain OCC
• Intra-symbol pre-DFT-s OCC (comb-like structure as in PUCCH format 4)
• Combinations of OCC techniques
• TBoMS for OCC techniques is FFS

R1-2403423         Feature lead summary #2 of AI 9.11.3 on NR-NTN uplink capacity and throughput Moderator (MediaTek)

From Thursday session

Agreement

RAN1 to at least further study the potential specification aspects on OCC techniques:

·       TBS calculation / Rate matching

·       UCI multiplexing

·       RV cycling across repetitions

·       Frequency hopping, e.g. intra /inter slot

·       OCC indication/configuration

·       Power control

·       FFS others aspects

Final summary in R1-2403721.

9.11.44    IoT-NTN uplink capacity/throughput enhancement

R1-2402006         Discussion on UL capacity enhancements for IoT NTN              Huawei, HiSilicon

R1-2402123         Discussion on IoT-NTN uplink capacity/throughput enhancement              Spreadtrum Communications

R1-2402176         IoT-NTN uplink capacity/throughput enhancement    InterDigital, Inc.

R1-2402262         Discussion on IoT-NTN uplink capacity enhancement              vivo

R1-2402346         Discussion on IoT-NTN uplink capacity/throughput enhancement              OPPO

R1-2402375         Discussion on UL capacity enhancement for IoT NTN              CATT

R1-2402486         Discussion on uplink capacity/throughput enhancement for IoT-NTN      Samsung

R1-2402583         Discussion on the IoT -NTN uplink capacity/throughput enhancements      CMCC

R1-2402590         Discussion on uplink capacity enhancement for IoT NTN              Lenovo

R1-2402625         Discussion on UL capacity enhancement for IoT NTN              ZTE

R1-2402658         Discussion on IoT-NTN uplink capacity enhancement              Xiaomi

R1-2402774         IoT-NTN uplink capacity/throughput enhancement    NEC

R1-2402814         Discussion on IoT-NTN uplink capacity/throughput enhancement              LG Electronics

R1-2402905         On IoT-NTN Uplink Capacity Enhancement Apple

R1-2402917         IoT NTN OCC methods for NPUSCH and NPRACH  Sharp

R1-2402937         Discussion on IoT-NTN uplink capacity and throughput              MediaTek

R1-2402994         IoT-NTN uplink capacity enhancement         Nokia, Nokia Shanghai Bell

R1-2403005         On uplink capacity enhancements for IoT-NTN           Ericsson

R1-2403032         Discussion on IoT-NTN uplink capacity/throughput enhancement              ETRI

R1-2403444         IOT-NTN uplink capacity - throughput enhancement Qualcomm Incorporated        (rev of R1-2403214)

R1-2403560         FL Summary #1 for IoT-NTN       Moderator (Sony)

From Tuesday session

Agreement

For the NPUSCH evaluation assumptions, update the DMRS configuration, as follows:

Agreement

At least the following NPRACH OCC schemes are considered by RAN1 for study:

• Intra-symbol group OCC
• Inter-symbol group(s) OCC
• Inter-repetition OCC

Agreement

The study of OCC for NPRACH does not consider NPRACH format 2.

Agreement

·       The following evaluation assumptions are used for the study of OCC for NPRACH:

Agreement

OCC multiplexing is not supported between a UE using NPUSCH format 1 with 3.75kHz SCS and another UE using NPUSCH format 1 with 15kHz SCS.

R1-2403719         FL Summary #2 for IoT-NTN       Moderator (Sony)

From Thursday session

Agreement

For OCC of NPUSCH format 1, RAN1 will not consider multiplexing more than 4 UEs.

Agreement

For single-tone DMRS when OCC is applied to NPUSCH format 1, RAN1 considers at least the following for further study:

• TDM of DMRS. The time domain locations of DMRS for different UEs are different. No OCC is applied for the DMRS of different UEs.
• FFS: Detailed mapping
• CDM of DMRS. The time domain locations of DMRS for different UEs are the same. Different OCCs are applied for the DMRS of different UEs.
• FFS: Detailed mapping
• Other schemes are not precluded, including combinations of the above

Agreement

For the NPUSCH evaluation assumptions, update the frequency error assumption, as follows.

 RAN1#117

9.11   Non-Terrestrial Networks (NTN) for NR Phase 3 and Internet of Things (IoT) Phase 3

Please refer to RP-240775 for detailed scope of the WI for NR-NTN Phase 3. Please refer to RP-234077 for detailed scope of the WI for IoT-NTN Phase 3.

R1-2405699         Session notes for 9.11 (Non-Terrestrial Networks for NR Phase 3 and Internet of Things Phase 3)    Ad-Hoc Chair (Huawei)

Friday decision: The session notes are endorsed and contents reflected below.

[117-R19-NTN] – Mohamed (Thales)

Email discussion on Rel-19 NTN enhancement

-        To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2404205         Work plan for Rel-19 NR_NTN_Ph3             THALES

9.11.1    NR-NTN downlink coverage enhancement

R1-2405421         Discussion on downlink coverage enhancements for NR NTN              Huawei, HiSilicon             (rev of R1-2403938)

R1-2403989         On NR-NTN downlink coverage enhancement           Ericsson

R1-2403993         Further considerations on FR2-NTN analysis assumptions              Eutelsat Group

R1-2404003         Discussion on downlink coverage enhancements for NR NTN              Fraunhofer IIS, Fraunhofer HHI

R1-2404041         Discussion on NR-NTN downlink coverage enhancement              Spreadtrum Communications

R1-2404132         Discussion on downlink coverage enhancement for NR-NTN              Samsung

R1-2404194         Discussion on NR-NTN downlink coverage enhancement              vivo

R1-2405342         Discussion on NR NTN Downlink coverage enhancements              THALES, Magister           (rev of R1-2404201)

R1-2404214         Discussion on DL coverage enhancement for NR NTN              ZTE

R1-2404261         NR-NTN downlink coverage enhancement   InterDigital, Inc.

R1-2404307         Discussion on NR-NTN Downlink Coverage Enhancement              Apple

R1-2404323         Discussion on NR-NTN downlink coverage enhancement        LG Electronics

R1-2404390         Performance evaluation of downlink coverage enhancement for NR NTN              CATT

R1-2404441         Discussion on downlink coverage enhancement for NR NTN              Lenovo

R1-2404471         Discussion on NR-NTN DL coverage enhancement    CMCC

R1-2404607         Discussion on NR-NTN downlink coverage enhancement              Xiaomi

R1-2404670         NR-NTN downlink coverage enhancement   NEC

R1-2404692         Downlink Coverage Enhancement for NR NTN          Google

R1-2404694         Beam group for NR-NTN downlink coverage enhancement               Sharp

R1-2404784         Discussion on NR-NTN downlink coverage enhancement              ETRI

R1-2404789         Discussion on downlink coverage enhancement for NR NTN              Baicells (Late submission)

R1-2404861         Discussion on NR-NTN downlink coverage enhancement              OPPO

R1-2404916         Discussion on NR NTN Downlink Coverage Enhancements     IIT Kharagpur, CEWIT

R1-2405057         Discussion on DL coverage enhancement for NR-NTN              NTT DOCOMO, INC.

R1-2405090         Discussion on NR-NTN downlink coverage enhancement              MediaTek Inc.

R1-2405117         NR-NTN Downlink Coverage Enhancement Panasonic

R1-2405172         Downlink coverage enhancement for NR NTN            Qualcomm Incorporated

R1-2405226         Discussion on DL coverage enhancements for NR-NTN              NICT

R1-2405251         Downlink Coverage Enhancements for NR NTN        CEWiT

R1-2405257         Discussion on downlink coverage enhancement for NR-NTN              CSCN

R1-2405263         Downlink coverage enhancements for NR over NTN  Nokia, Nokia Shanghai Bell

R1-2404202         FL Summary #1: NR-NTN downlink coverage enhancements              Moderator (THALES)

From Tuesday session

Observation

Based on LLS results on PDCCH coverage evaluation collected from different sources:

• It is observed that the required SNR for PDCCH is in average equal to -6dB (17 sources)
• With parameter LEO600km Set1-1 FR1 and 1-2 FR1:
• 17 sources observed that there is no coverage gap with Set1-1/1-2 FR1.
• The coverage margin is around 4 dB compared to CNR of -1.9 dB.
• With parameter LEO600km Set1-3 FR1:
• 15 sources observed that there is a PDCCH coverage gap of 3.9dB in average compared to CNR of -9.9 dB.
• Note: the results above are obtained independently from the performance of other channels or signals, and it doesn’t imply the successful reception for other channels or signals before or after the detection of PDCCH.

Observation

Based on LLS results on PDSCH Msg2 coverage evaluation collected from different sources:

• It is observed that the required SNR for PDSCH carrying Msg2 is in average equal to – 10.9 dB (14 sources)
• With parameter LEO600km Set1-1 FR1 and 1-2 FR1:
• 14 sources observed that there is no coverage gap for PDSCH with Msg2:
• The coverage margin is around 9 dB compared to CNR of -1.9 dB 
• With parameter LEO600km Set1-3 FR1:
• 12 sources observed that there is no coverage gap for PDSCH with Msg2:
• The coverage margin is around 1 dB on average compared to CNR of -9.9 dB
• Note: the results above are obtained independently from the performance of other channels or signals, and it doesn’t imply the successful reception for other channels or signals before or after the detection of PDSCH Msg2.

Observation

Based on LLS results on PDSCH Msg4 coverage evaluation collected from different sources:

• It is observed that the required SNR for PDSCH carrying Msg4 is in average equal to – 5.2 dB (14 sources)
• With parameter LEO600km Set1-1 FR1 and 1-2 FR1:
• 14 sources observed that there is no coverage gap for PDSCH with Msg4:
• The coverage margin is around 3.3 dB on average compared to CNR of -1.9 dB
• With parameter LEO600km Set1-3 FR1:
• 11 sources observed that there is a coverage gap for PDSCH with Msg4:
• The coverage gap is around 4.7 dB on average compared to CNR of -9.9 dB
• 1 source observed that there is no coverage gap for PDSCH with Msg4 with a coverage margin of 0.3 dB compared to CNR of -9.9 dB
• Note: the results above are obtained independently from the performance of other channels or signals, and it doesn’t imply the successful reception for other channels or signals before or after the detection of PDSCH Msg4.

R1-2404203         FL Summary #2: NR-NTN downlink coverage enhancements              Moderator (THALES)

From Thursday session

Observation

Based on LLS results on PDSCH SIB1 coverage evaluation collected from different sources:

• For PDSCH carrying SIB1 option 1 (with a payload size of 800bits) it is observed that the required SNR is in average equal to – 5.8 dB (14 sources)
• For PDSCH carrying SIB1 option 2 (with a payload size of 1280bits) it is observed that the required SNR is in average equal to – 3.4 dB (12 sources)
• With parameter LEO600km Set1-1 FR1 and 1-2FR1:
• 14 sources observed that there is no coverage gap for PDSCH with SIB1 option 1:
• The coverage margin is around 3.9 dB on average compared to CNR of -1.9 dB
• 12 sources observed that there is no coverage gap for PDSCH with SIB1 option 2:
• The coverage margin is around 1.5 dB on average compared to CNR of -1.9 dB
• With parameter LEO600km Set1-3 FR1:
• 11 sources observed that there is a coverage gap for PDSCH with SIB1 option 1:
• The coverage gap is around 4.1 dB on average compared to CNR of -9.9 dB
• 1 source observed that there is no coverage gap for PDSCH with SIB1 option 1:
• The coverage margin is 3.4 dB compared to CNR of -9.9 dB
• 10 sources observed that there is a coverage gap for PDSCH with SIB1 option 2:
• The coverage gap is around 6.5 dB on average compared to CNR of -9.9 dB
• Note: some results assumed SIB1 combination (where SIB1 is repeated within 160 ms) and some results assumed no SIB1 combination
• Note: the results above are obtained independently from the performance of other channels or signals, and it doesn’t imply the successful reception for other channels or signals before or after the detection of PDSCH carrying SIB1.

Observation

Based on LLS results on PDSCH SIB19 coverage evaluation collected from different sources:

• It is observed that the required SNR for PDSCH carrying SIB19 is in average equal to – 6.9 dB (14 sources)
• With parameter LEO600km Set1-1 FR1 and 1-2 FR1:
• 12 sources observed that there is no coverage gap for PDSCH with SIB19:
• The coverage margin is around 4.2 dB on average compared to CNR of -1.9 dB 
• With parameter LEO600km Set1-3 FR1:
• 10 sources observed that there is a coverage gap for PDSCH with SIB19:
• The coverage gap is around 3.5 dB on average compared to CNR of -9.9 dB
• Note: all the results above assumed no SIB19 combination
• Note: the results above are obtained independently from the performance of other channels or signals, and it doesn’t imply the successful reception for other channels or signals before or after the detection of PDSCH carrying SIB19.

R1-2404204         FL Summary #3: NR-NTN downlink coverage enhancements              Moderator (THALES)

From Friday session

Observation

Based on the results of DL coverage ratio evaluation at system level collected from 7 sources for all the three LEO600km satellite parameter sets where the beam footprint diameter is 50 km:

·       For Set 1-1/1-3, the coverage ratio can be improved from 10% to 100% if the SSB periodicity is increased from 20ms to 80ms and beam hopping is applied

·       For Set 1-2, the coverage ratio can be improved from 1.5% to 96.8% if the SSB periodicity is increased from 20ms to 320ms and beam hopping is applied.

·       Note: coverage ratio is N2+N3/ total beam footprints

·       Note: the baseline assumes no beam hopping. TDM between SIB1 and SIB19 is assumed in those results, following current specs.

Based on the results of DL coverage ratio evaluation at system level collected from 3 sources for a deployment scenario implementing wide beam footprint:

·       1 source reports that with a deployment of wide beam covering 4 narrow (of 50km size) beams, which means Set 1-2 FR1 with additional EIRP reduction of 6dB, using SSB periodicity of 80 ms can provide coverage ratio of 96.8%, and Set 1-1/1-3 FR1 with additional EIRP reduction of 6dB, SSB periodicity of 80 ms can provide coverage of 100%.

·       1 source observed that for Set 1-1, 1-2 and 1-3, the coverage ratio can be improved from 1.5% to 100% using the legacy default SSB periodicity of 20ms during initial access, by choosing a wide beam footprint with beam footprint sizes of 84 km and 56 km respectively.

o   Note: the PDCCH and the PDSCH for SIB19 is assumed to be transmitted within 2 OFDM symbols and 5 MHz bandwidth. the PDSCH for SIB1 is assumed to be transmitted within 3 OFDM symbols and 5 MHz bandwidth. This assumes no SIB1 and SIB19 transmission in N2 beam footprints. This assumes non-aligned SFN timing across different beams.

·       1 source observed, for Set 1-1 with increased beam size, that the legacy SSB periodicity of 20ms during initial access is usable with NTN beam hopping, by choosing a deployment scenario implementing wide beam footprint with beam footprint sizes of 70.7 km and 86.6 km, leading to a total of 529 and 353 beam footprints within the satellite coverage area, respectively, and the coverage ratio is 80% and 90%, respectively, and a ratio of simultaneously active beam footprints to the total number of beam foot prints equal to 20% and 30%.

o   Note: Beam footprint size is increased by increasing only the adjacent beam spacing without increasing the 3dB beamwidth.

Note: RAN1 will further investigate the impact of SSB periodicity extension

Note: Any needed clarification “SSB channel enhancement is not considered” in the WID is up to RAN plenary

Note: RAN1 will further investigate the impact of wider beam of SSB and/or other channels on performance (e.g. link budget, capacity...)

Observation

Based on LLS results on PDSCH for VoIP coverage evaluation collected from different sources:

• It is observed that the required SNR for PDSCH for VoIP is in average equal to – 11 dB (11 sources)
• With parameter LEO600km Set1-1 and 1-2 FR1:
• When PDSCH repetition is enabled, 11 sources observed that there is no coverage gap for VoIP:
• The coverage margin is around 9.1 dB on average, compared to CNR of -1.9 dB  
• With parameter LEO600km Set1-3 FR1:
• When PDSCH repetition is enabled, 9 sources observed that there is no coverage gap for VoIP:
• The coverage margin is around 2.3 dB on average, compared to CNR of -9.9 dB
• 1 source observed that even with 8 PDSCH repetitions there is a coverage gap of 1.5 dB compared to CNR of -9.9 dB
• Note: the results above are obtained independently from the performance of other channels or signals, and it doesn’t imply the successful reception for other channels or signals before or after the detection of PDSCH for VoIP.

Observation

Based on LLS results on PDSCH 3kbps coverage evaluation collected from different sources:

• It is observed that the required SNR for PDSCH for low data rate is in average equal to – 11 dB (8 sources)
• With parameter LEO600km Set1-1 FR1 and 1-2 FR1:
• When PDSCH repetition is enabled, 8 sources observed that there is no coverage gap for PDSCH with 3kbp:
• The coverage margin is around 9.1 dB on average, compared to CNR of -1.9 dB  
• With parameter LEO600km Set1-3 FR1:
• When PDSCH repetition is enabled, 6 sources observed that there is no coverage gap for PDSCH with 3kbp:
• The coverage margin is around 1.6 dB on average, compared to CNR of -9.9 dB
• Note: the results above are obtained independently from the performance of other channels or signals, and it doesn’t imply the successful reception for other channels or signals before or after the detection of PDSCH 3kbps.

Observation

Based on LLS results on PDSCH 1Mbps coverage evaluation collected from different sources:

• It is observed that the required SNR for PDSCH with 1Mbps data rate is in average equal to – 4.1 dB (7 sources)
• With parameter LEO600km Set1-1 FR1 and 1-2 FR1:
• 7 sources observed that there is no coverage gap for PDSCH with 1Mbps:
• The coverage margin is around 2.2 dB on average, compared to CNR of -1.9 dB  
• With parameter LEO600km Set1-3 FR1:
• 5 sources observed that, there is a coverage gap for PDSCH with 1Mbps:
• The coverage gap is around 5.5 dB on average, compared to CNR of -9.9 dB
• Note: the results above are obtained independently from the performance of other channels or signals, and it doesn’t imply the successful reception for other channels or signals before or after the detection of PDSCH 1Mbps.

Final summary in R1-2405730.

9.11.2    Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands

Work in RAN1 is limited to checking whether any essential changes are needed for their support (i.e. focusing on HD collision rules) by end of Q2/2024.

R1-2403939         Discussion on HD-FDD RedCap UEs and eRedCap UEs for FR1-NTN      Huawei, HiSilicon

R1-2404042         Discussion on support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands Spreadtrum Communications

R1-2404133         Discussion on support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands Samsung

R1-2404195         Discussion on support of RedCap and eRedCap UEs with NR-NTN      vivo

R1-2404215         Discussion on support of RedCap/eRedCap UEs for NR NTN              ZTE

R1-2404262         Discussion on half-duplex RedCap issues for NTN FR1 operation              InterDigital, Inc.

R1-2404308         Discussion on support of RedCap UEs with NR NTN operation              Apple

R1-2404324         Discussion on support of (e)RedCap UEs with NR-NTN operating in FR1-NTN bands            LG Electronics

R1-2404391         Discussion on the operation of RedCap and eRedCap UEs In NTN              CATT

R1-2404438         Discussion on Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands China Telecom

R1-2404472         Discussion on the collision issues of HD-FDD Redcap UE in FR1-NTN             CMCC

R1-2404533         On HD-FDD Redcap UEs for NTN Ericsson

R1-2404580         Discussion on support of RedCap/eRedCap UEs in NR NTN              HONOR

R1-2404608         Discussion on the support of Redcap UE for NTN operating on FR1 bands            Xiaomi

R1-2404725         Discussion on support of RedCap/eRedCap UEs in NTN              CAICT

R1-2404736         Discussion on HD-FDD RedCap UEs and eRedCap UEs for FR1-NTN      TCL

R1-2404785         Discussion on HD UEs with NR NTN           ETRI

R1-2404862         Discussion on supporting of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands OPPO

R1-2405058         Discussion on support of RedCap and eRedCap UEs in FR1-NTN              NTT DOCOMO, INC.

R1-2405091         Discussion on support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands MediaTek Inc.

R1-2405173         Support of Redcap and eRedcap UEs in NR NTN       Qualcomm Incorporated

R1-2405264         Considerations on (e)RedCap operation in NR over NTN              Nokia, Nokia Shanghai Bell

R1-2405516         Summary #1 for Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands      Moderator (CATT)

From Tuesday session

Conclusion

For Rel-19 HD-FDD RedCap/eRedCap UE in NTN, the issues caused by TA mismatch between actual TA used by the UE and assumed TA for the UE at the gNB should be mitigated for collision cases 3 and 4.

·       Note: further discussion on other cases is not precluded.

R1-2405517         Summary #2 for Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands      Moderator (CATT)

From Thursday session

Conclusion

For collision cases 1, 2, 5 and 6, the existing priority rules can be reused for a HD-FDD (e)RedCap UE in NTN.

Observation

TA reporting is beneficial to mitigate the TA mismatch between actual TA used by the UE and assumed TA for the UE at the gNB for HD-FDD RedCap/eRedCap UE in NTN from RAN1 perspective.

·       Note: complexity, power consumption and signaling overhead impact of TA reporting for (e)redcap UEs was not investigated in this work item

Final summary in R1-2405741.

9.11.3    NR-NTN uplink capacity/throughput enhancement

R1-2405550         Discussion on uplink capacity/throughput enhancement for FR1-NTN      Huawei, HiSilicon             (rev of R1-2403940           )

R1-2404043         Discussion on NR-NTN uplink capacity/throughput enhancement              Spreadtrum Communications

R1-2404134         Discussion on uplink capacity/throughput enhancement for NR-NTN      Samsung

R1-2404196         Discussion on NR-NTN uplink capacity enhancement              vivo

R1-2404216         Discussion on UL capacity enhancement for NR NTN              ZTE

R1-2404263         NR-NTN uplink capacity/throughput enhancement    InterDigital, Inc.

R1-2404309         Discussion on NR-NTN Uplink Capacity Enhancement              Apple

R1-2404315         Views on NR-NTN PUSCH capacity enhancement    Mitsubishi Electric RCE

R1-2404319         NTN NR uplink capacity enhancement         Sharp

R1-2404325         Discussion on NR-NTN uplink capacity/throughput enhancement              LG Electronics

R1-2404392         Discussion on UL capacity enhancement for NR NTN              CATT

R1-2404418         On uplink capacity/throughput enhancement for NR NTN              Ericsson

R1-2404439         Discussion on NR-NTN uplink enhancement              China Telecom

R1-2404473         Discussion on the NR-NTN uplink capacity/throughput enhancements      CMCC

R1-2404609         Discussion on NR-NTN PUSCH capacity enhancement              Xiaomi

R1-2404671         NR-NTN uplink capacity/throughput enhancement    NEC

R1-2404693         Uplink Capacity Enhancement for NR NTN  Google

R1-2404786         Discussion on NR-NTN uplink capacity/throughput enhancement              ETRI

R1-2404801         Discussion on uplink capacity/throughput enhancement for NR-NTN      Lenovo

R1-2404806         Discussion on uplink capacity/throughput enhancement for FR1-NTN      Fujitsu

R1-2404863         Discussion on NR-NTN uplink capacity/throughput enhancement              OPPO

R1-2404976         Discussion on the NR-NTN uplink capacity/throughput enhancements      TCL

R1-2405011         Uplink capacity/throughput enhancement for NR-NTN              Panasonic

R1-2405059         Discussion on NR-NTN uplink capacity/throughput enhancement              NTT DOCOMO, INC.

R1-2405092         Discussion on NR-NTN uplink capacity and throughput              MediaTek Inc.

R1-2405174         NR-NTN uplink capacity / throughput enhancement   Qualcomm Incorporated

R1-2405227         Discussion on NR-NTN uplink capacity/throughput enhancement              NICT

R1-2405265         Uplink capacity enhancement considerations for NR over NTN              Nokia, Nokia Shanghai Bell

R1-2405506         Feature lead summary #1 of AI 9.11.3 on NR-NTN uplink capacity and throughput Moderator (MediaTek)

Presented in Monday session.

R1-2405507         Feature lead summary #2 of AI 9.11.3 on NR-NTN uplink capacity and throughput Moderator (MediaTek)

From Wednesday session

Agreement

For the normative phase, at least one of the OCC techniques will be specified:

·       Inter-slot time-domain OCC with PUSCH repetition Type A with OCC length 2 or 4

·       Inter-symbol(s) time domain OCC with OCC length 2 or 4

·       Intra-symbol pre-DFT-s OCC (comb-like structure as in PUCCH format 4) with OCC length 2 or 4

·       FFS Combination of OCC techniques including multiplexing of 8 UEs

·       FFS Use of OCC techniques with TBoMS

·       FFS Backward compatibility with non-Rel-19 UEs

R1-2405593         Feature lead summary #3 of AI 9.11.3 on NR-NTN uplink capacity and throughput Moderator (MediaTek)

Presented in Thursday session

R1-2405648         Feature lead summary #4 of AI 9.11.3 on NR-NTN uplink capacity and throughput Moderator (MediaTek)

From Friday session

Conclusion

OCC with PUSCH can support at least multiplexing of 2 or 4 UEs and achieve up to 2 or 4 times capacity gains respectively, when repetitions are used.

Note: the actual gain may be less due to e.g. intra/inter cell interference.

Final summary in R1-2405685.

9.11.44    IoT-NTN uplink capacity/throughput enhancement

R1-2403941         Discussion on UL capacity enhancements for IoT NTN              Huawei, HiSilicon

R1-2404044         Discussion on IoT-NTN uplink capacity/throughput enhancement              Spreadtrum Communications

R1-2404135         Discussion on uplink capacity/throughput enhancement for IoT-NTN      Samsung

R1-2404197         Discussion on IoT-NTN uplink capacity enhancement              vivo

R1-2404217         Discussion on UL capacity enhancement for IoT NTN              ZTE

R1-2404264         IoT-NTN uplink capacity/throughput enhancement    InterDigital, Inc.

R1-2404310         Discussion on IoT-NTN Uplink Capacity Enhancement              Apple

R1-2404326         Discussion on IoT-NTN uplink capacity/throughput enhancement              LG Electronics

R1-2404393         Discussion on UL capacity enhancement for IoT NTN              CATT

R1-2404442         Discussion on uplink capacity enhancement for IoT NTN              Lenovo

R1-2404474         Discussion on the IoT -NTN uplink capacity/throughput enhancements      CMCC

R1-2404534         On uplink capacity enhancements for IoT-NTN           Ericsson

R1-2404610         Discussion on IoT-NTN uplink capacity enhancement              Xiaomi

R1-2404672         IoT-NTN uplink capacity/throughput enhancement    NEC

R1-2404695         IoT NTN OCC multiplexing methods for NPUSCH and NPRACH              Sharp

R1-2404742         IoT-NTN uplink capacity enhancement         Nokia, Nokia Shanghai Bell

R1-2404787         Discussion on uplink capacity/throughput enhancement for IoT NTN      ETRI

R1-2404864         Discussion on IoT-NTN uplink capacity/throughput enhancement              OPPO

R1-2405093         Discussion on IoT-NTN uplink capacity and throughput              MediaTek Inc.

R1-2405175         IOT-NTN uplink capacity/throughput enhancement   Qualcomm Incorporated

R1-2405178         Discussion on the IoT-NTN uplink capacity/throughput enhancements      TCL

R1-2405493         FL Summary #1 for IoT-NTN       Moderator (Sony)

Agreement

For 3.75kHz single-tone OCC for NPUSCH format 1, RAN1 supports either symbol-level OCC or slot-level OCC. Other OCC schemes are not pursued.

For 15kHz single-tone OCC for NPUSCH format 1, RAN1 supports either symbol-level OCC or slot-level OCC. Other OCC schemes are not pursued.

R1-2405494         FL Summary #2 for IoT-NTN       Moderator (Sony)From Monday session

From Wednesday session

Agreement

Inter-repetition OCC for NPRACH is not studied further in RAN1.

Agreement

• For the time-domain DMRS pattern (including blanked DMRS, if any):
• For 15kHz single-tone, RAN1 strives to reuse the Rel-17 DMRS pattern.
• For 3.75kHz single-tone
•  RAN1 studies
• Rel-17 DMRS pattern
• A new DMRS pattern
• The DMRS overhead (including blanked DMRS, if any) for OCC is the same as for Rel-17.

Agreement

The Rel-17 guard period locations and length for NB-IoT 3.75kHz UL slot are preserved when OCC is applied to NPUSCH format 1.

 RAN1#118

9.11   Non-Terrestrial Networks (NTN) for NR Phase 3 and Internet of Things (IoT) Phase 3

Please refer to RP-241667 for detailed scope of the WI for NR-NTN Phase 3. Please refer to RP-241624 for detailed scope of the WI for IoT-NTN Phase 3.

R1-2407482         Session notes for 9.11 (Non-Terrestrial Networks for NR Phase 3 and Internet of Things Phase 3)    Ad-Hoc Chair (Huawei)

Friday decision: The session notes are endorsed and contents reflected below.

[118-R19-NTN] – Mohamed (Thales)

Email discussion on Rel-19 NTN enhancement

-        To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2406439         Work plan for Rel-19 NR_NTN_Ph3             THALES

From AI 5

R1-2405786         LS on UL synchronization for contention based Msg3 transmission without Msg1/Msg2 RAN2, ZTE

Decision: To be moderated Fangyu (ZTE).

R1-2407384         Summary for Reply LS on UL synchronization for contention based Msg3 transmission without Msg1/Msg2        Moderator (ZTE)

Presented in Wednesday session.

R1-2407521         Summary for Reply LS on UL synchronization for contention based Msg3 transmission without Msg1/Msg2        Moderator (ZTE)

From Friday session

Agreement

RAN1’s response to Q1 is endorsed as below:

From RAN1 perspective, assuming Note 1 and Note 2 are satisfied, an RRC Idle UE with a pre-compensated TA (i.e., the one used for Msg1 transmission during random access for IoT NTN) can satisfy requirement for Msg3 transmission/reception without Msg1/Msg2 at least in the following cases:

·         NB-IoT with 3.75kHz SCS.

·         eMTC CE mode A.

Note 1: RAN1 assumes N_TA=0 for Msg3 transmission without Msg1/Msg2

Note 2: RAN1 assumes that the RAN4 UL synchronization requirements specified in Table 7.20A.2-1 and Table 7.24A.2-1 of TS 36.133 apply to the Msg3 transmission without Msg1/Msg2 in NB-IoT over NTN and eMTC over NTN, respectively.

Note 3: RAN1 may further discuss the cases of NB-IoT with 15kHz SCS and eMTC CE mode B

Action to RAN2: RAN1 respectfully asks RAN2 to take the response into account.

Action to RAN4: RAN1 respectfully asks RAN4 to confirm whether RAN1’s assumptions in Note 1 and Note 2 are valid.

R1-2407546         Draft Reply LS on UL synchronization for contention based Msg3 transmission without Msg1/Msg2

Decision: The draft LS in R1-2407546 is endorsed. Final LS is approved in R1-2407548.

9.11.1    NR-NTN downlink coverage enhancement

R1-2405834         On NR-NTN downlink coverage enhancement           Ericsson

R1-2405838         Discussion on downlink coverage enhancements for NR NTN              Huawei, HiSilicon

R1-2405891         Discussions on downlink coverage enhancements for NR NTN              Fraunhofer IIS, Fraunhofer HHI

R1-2405925         Discussion on NR-NTN downlink coverage enhancement              Spreadtrum Communications

R1-2406003         Discussion on NR-NTN DL coverage enhancement    CMCC

R1-2406052         Discussion on DL coverage enhancements for NR-NTN              NICT

R1-2406108         NR-NTN downlink coverage enhancement   InterDigital, Inc.

R1-2406130         Discussion on DL coverage enhancement for NR NTN              ZTE Corporation, Sanechips

R1-2406202         Discussion on NR-NTN downlink coverage enhancement              vivo

R1-2406229         Discussion on NR-NTN downlink coverage enhancement              OPPO

R1-2406275         Discussion on NR-NTN downlink coverage enhancement              Xiaomi

R1-2406359         Further consideration on downlink coverage enhancement for NR NTN      CATT

R1-2406434         Discussion on NR NTN Downlink coverage enhancements              THALES

R1-2406446         Discussion on NR-NTN downlink coverage enhancement        LG Electronics

R1-2406452         Discussion on NR NTN Downlink Coverage Enhancements              IIT, Kharagpur

R1-2406511         Discussion on downlink coverage enhancement for NR NTN              Lenovo

R1-2406554         NR-NTN downlink coverage enhancement   NEC

R1-2406572         NR-NTN downlink coverage enhancement with beam groups              Sharp

R1-2406584         Discussion on NR-NTN downlink coverage enhancement              HONOR

R1-2406592         Discussion on downlink coverage enhancement for NR NTN              Baicells

R1-2406615         NR-NTN Downlink Coverage Enhancement Panasonic

R1-2406670         Discussion on downlink coverage enhancement for NR-NTN              Samsung

R1-2406738         Discussion on NR-NTN downlink coverage enhancement              ETRI

R1-2406754         Downlink coverage enhancements for NR over NTN  Nokia, Nokia Shanghai Bell

R1-2406777         NR-NTN - downlink coverage enhancement MediaTek Inc.

R1-2406863         On NR-NTN Downlink Coverage Enhancement         Apple

R1-2406885         Discussion on NR-NTN DL coverage enhancement    KT Corp.

R1-2406900         Discussion on NR-NTN downlink coverage enhancement              TCL

R1-2406949         Discussion on DL coverage enhancement for NR-NTN              NTT DOCOMO, INC.

R1-2406965         Downlink Coverage Enhancement for NR NTN          Google Ireland Limited

R1-2407049         Downlink coverage enhancement for NR NTN            Qualcomm Incorporated

R1-2407078         Downlink Coverage Enhancements for NR NTN        CEWiT

R1-2407118         Discussion on downlink coverage enhancement for NR-NTN              CSCN

R1-2406435         FL Summary #1: NR-NTN downlink coverage enhancements              THALES

From Tuesday session

Observation

Based on the results of DL coverage evaluation at system level collected from different sources, it is observed that extending the default value of SSB periodicity (different from 20ms) in NTN with LEO600km satellite parameter sets where the beam footprint diameter is 50 km, is beneficial in terms of reduction of common control channel overhead, when targeting a full coverage of 1058 beam footprints:

·         With Set 1-1 FR1 and Set 1-3 FR1, the common messages (SSB, SIB1) overhead is around 40% assuming 5 MHz BW when SSB/SIB1 periodicity of 20ms is in use, this overhead ratio could be reduced to less than 14% when 160ms SSB/SIB1 periodicity is used.

·         With Set 1-2 FR1, the common message (SSB, SIB1) overhead is greater than 100% assuming 5 MHz BW when SSB/SIB1 periodicity of 20ms is in use, this overhead could be reduced to around 25.8% when 640ms SSB/SIB1 periodicity is used.

·         Note: the overhead of SIB19 was included in some of the results.

·         Note: an observation when SSB/SIB1 periodicity is 320 ms will be discussed and added to the observation.

R1-2406436         FL Summary #2: NR-NTN downlink coverage enhancements              THALES

From Thursday session

Agreement

As part of the NTN DL coverage enhancements at both system level and link level, RAN1 to consider:

• Extending the periodicity of the half frames with SS/PBCH blocks assumed by UE during initial access.
• Default value[s] with extended periodicity assumed by NTN UE for initial access can be:
• One [or more] values from the list {40ms, 80 ms, 160 ms, 320ms, 640ms}
• Potential enhancements for transmitting the DL common channels using a wider beam footprint, while DL/UL dedicated channels (incl. PRACH) may be transmitted using a narrower beam footprint
• Link-level enhancements for the following channels:
• PDCCH
• PDSCH with Msg 4
• PDSCH with SIB1/SIB19.
• Note: link-level enhancements for PDSCH with SIB1/SIB19 may be applicable to other SIBs, without additional specification impact.
• Note: the above does not imply that all the channels above will be enhanced, but all of them should be considered based on this agreement

Final summary in R1-2406437.

From AI 5

R1-2405785         LS on DL coverage enhancements              RAN2, CMCC

Decision: To be moderated by Yi (CMCC).

R1-2407455         Draft Reply LS on DL coverage enhancements           CMCC

R1-2407456         Moderator’s summary on the discussion of the reply LS on DL coverage enhancements           Moderator (CMCC)

From Thursday session

Proposal (Answer to Q3):

The solutions of beam hopping are still under RAN1’s discussion. RAN1 has not discussed beam hopping for uplink.

Agreement (Answer to Q4):

RAN1 confirms the RAN2 understanding that satellite beams are currently not visible to UEs. Beam footprint status in terms of "off", "common messages only" and "active traffic” in one of the RAN1 agreements is only defined for the sake of system-level evaluation methodology. Currently there is no intention to define beam status for beams not visible to the UE or to define new beam status for beams visible to the UE.

Proposal (Answer to Q5):

Currently there is no intention to define new beam status for beams visible to the UE.

Agreement (Answer to Q1):

According to the updated WID (RP-241667), SSB enhancement other than SSB periodicity extension is not considered. Thereby, RAN1 understanding is that enhancements to the existing SSB patterns, e.g. SSB position in burst, SSB index number, are not within the scope.

The extension of the SSB periodicity is still under RAN1’s discussion.

Proposal (Answer to Q2):

Currently RAN1 does not have any conclusion on the enhancements to the common control channel.

If the SSB periodicity extension is introduced, the transmission of broadcast information including SIB1 and other system information may will be extended accordingly.

Comeback for draft LS (Yi, CMCC)

R1-2407455         Draft Reply LS on DL coverage enhancements       CMCC

From Friday session

Agreement

The draft LS in R1-2407455 is endorsed with the following revision:

·         RAN1 will try to provide a further response at a later timeThe other questions would be replied when RAN1 has more progresses.

·         Add the R1 Tdoc number of incoming LS to the cover page

Final LS is approved in R1-2407538.

9.11.2    Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands

R1-2405839         Discussion on HD-FDD RedCap UEs and eRedCap UEs for FR1-NTN      Huawei, HiSilicon

R1-2405926         Discussion on support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands Spreadtrum Communications

R1-2406004         Discussion on the collision issues of HD-FDD Redcap UE in FR1-NTN             CMCC

R1-2406100         Discussion on Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands China Telecom

R1-2406109         Discussion on half-duplex RedCap issues for NTN FR1 operation              InterDigital, Inc.

R1-2406131         Discussion on support of RedCap/eRedCap UEs for NR NTN              ZTE Corporation, Sanechips

R1-2406203         Discussion on support of RedCap and eRedCap UEs with NR-NTN      vivo

R1-2406230         Discussion on supporting of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands OPPO

R1-2406276         Discussion on the support of Redcap UE in NR NTN  Xiaomi              Late submission

R1-2406360         Discussion on the enhancement of RedCap and eRedCap UEs In NTN      CATT

R1-2406447         Discussion on support of €RedCap Ues with NR-NTN operating in FR1-NTN bands            LG Electronics

R1-2406585         Discussion on support of RedCap/eRedCap UEs in NR NTN              HONOR

R1-2406671         Discussion on support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands Samsung

R1-2406739         Discussion on HD Ues with NR NTN            ETRI

R1-2406755         Considerations on €RedCap operation in NR over NTN              Nokia, Nokia Shanghai Bell

R1-2406778         NR-NTN – Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands           MediaTek Inc.

R1-2406808         On HD-FDD Redcap UEs for NTN Ericsson

R1-2406864         On support of RedCap UEs with NR NTN operation  Apple

R1-2406898         Discussion on support of RedCap/eRedCap UEs in NTN              CAICT

R1-2406901         Discussion on HD-FDD Redcap Ues and eRedcap UEs for FR1-NTN      TCL

R1-2406950         Discussion on support of RedCap and eRedCap UEs in FR1-NTN              NTT DOCOMO, INC.

R1-2407050         Support of Redcap and eRedcap UEs in NR NTN       Qualcomm Incorporated

R1-2407306         Summary #1 for Support of RedCap and eRedCap Ues with NR NTN operating in FR1-NTN bands      Moderator (CATT)

From Tuesday session

Agreement

The collision case 3 (Semi-statically configured DL reception collides with semi-statically configured UL transmission) can’t be assumed as error case. When the collision happens at UE side for collision case 3, one of the following options on priority rules is supported.

• Option A: the priority of keeping one direction and overriding another direction is based on different use cases (e.g. the collision happening in different channel types or different scheduling cases) without network signalling
• It is not precluded that some or all use cases are left to UE implementation regarding whether DL reception or UL transmission is dropped
• Note: it is not precluded that the same direction is prioritized for all different use cases
• Option B: network indicates the priority configuration to the UE
• It is not precluded that some use cases are left to UE implementation regarding whether DL reception or UL transmission is dropped
• It is not precluded to define default rules, if necessary

R1-2407307         Summary #2 for Support of RedCap and eRedCap Ues with NR NTN operating in FR1-NTN bands      Moderator (CATT)

From Thursday session

Agreement

To mitigate the collisions of case3 and case4, the following TA reporting enhancements for Rel-19 NTN HD-FDD (e)Redcap UE can be further studied:

·       Finer TA report granularity

·       Smaller TA offset threshold

·       Trigger a TA report when the collision is detected at the UE

·       TA reporting with a new triggering mechanism from gNB

·       TA drifting rate reporting

Note: The benefit, complexity, power consumption and signaling overhead of each scheme is to be further investigated.

Note: other solutions can also be studied.

Final summary in R1-2407498.

9.11.3    NR-NTN uplink capacity/throughput enhancement

R1-2405840         Discussion on uplink capacity/throughput enhancement for FR1-NTN      Huawei, HiSilicon

R1-2405927         Discussion on NR-NTN uplink capacity/throughput enhancement              Spreadtrum Communications

R1-2406005         Discussion on the NR-NTN uplink capacity/throughput enhancements      CMCC

R1-2406053         Discussion on NR-NTN uplink capacity/throughput enhancement              NICT

R1-2406076         Discussion on the NR-NTN uplink capacity/throughput enhancements      TCL

R1-2406101         Discussion on NR-NTN uplink enhancement              China Telecom

R1-2406110         NR-NTN uplink capacity/throughput enhancement    InterDigital, Inc.

R1-2406123         On uplink capacity/cell throughput enhancement for NR NTN              Ericsson

R1-2406132         Discussion on UL capacity enhancement for NR NTN              ZTE Corporation, Sanechips

R1-2406204         Discussion on NR-NTN uplink capacity enhancement              vivo

R1-2406231         Discussion on NR-NTN uplink capacity/throughput enhancement              OPPO

R1-2406277         Discussion on NR-NTN PUSCH capacity enhancement              Xiaomi

R1-2406361         Discussion on UL capacity enhancement for NR NTN              CATT

R1-2406448         Discussion on NR-NTN uplink capacity/throughput enhancement              LG Electronics

R1-2406513         Discussion on Uplink Capacity/Cell Throughput Enhancement for FR1-NTN             Fujitsu

R1-2406555         NR-NTN uplink capacity/throughput enhancement    NEC

R1-2406591         Uplink capacity/throughput enhancement for NR-NTN              Panasonic

R1-2406672         Discussion on uplink capacity/throughput enhancement for NR-NTN      Samsung

R1-2406740         Discussion on NR-NTN uplink capacity/throughput enhancement              ETRI

R1-2406756         Uplink capacity enhancement considerations for NR over NTN              Nokia, Nokia Shanghai Bell

R1-2406757         Discussion on uplink capacity/throughput enhancement for NR-NTN      Lenovo

R1-2406779         NR-NTN - uplink capacity/throughput enhancement  MediaTek Inc.

R1-2406802         NR-NTN uplink capacity enhancement         Sharp

R1-2406865         On NR-NTN Uplink Capacity Enhancement Apple

R1-2407222         Discussion on NR-NTN uplink capacity/throughput enhancement              NTT DOCOMO, INC.       (rev of R1-2406951)

R1-2406967         Uplink Capacity Enhancement for NR NTN  Google Ireland Limited

R1-2407051         NR-NTN uplink capacity / throughput enhancement   Qualcomm Incorporated

R1-2407139         Views on UL Capacity Enhancements for NR-NTN    Inmarsat, Viasat    Late submission

R1-2407206         Feature lead summary #1 of AI 9.11.3 on NR-NTN uplink capacity and throughput enhancements    Moderator (MediaTek)

From Wednesday session

Agreement

At least one of the OCC techniques when PUSCH repetitions are used will be specified:

• Inter-slot time-domain OCC with OCC length 2
• Inter-slot time-domain OCC with OCC length 2 and 4
• Intra-symbol pre-DFT-s OCC (comb-like structure as in PUCCH format 4) with OCC length 2
• Intra-symbol pre-DFT-s OCC (comb-like structure as in PUCCH format 4) with OCC length 2 and 4
• Note: combination of techniques is not precluded
• PUSCH repetition Type B is not considered

R1-2407207         Feature lead summary #2 of AI 9.11.3 on NR-NTN uplink capacity and throughput enhancements    Moderator (MediaTek)

From Friday session

Conclusion

Multiplexing of 8 UEs with PUSCH OCC is not discussed in RAN1 until the work for multiplexing of less than 8 UEs has been completed.

Final summary in R1-2407208.

9.11.44    IoT-NTN uplink capacity/throughput enhancement

R1-2405842         Discussion on UL capacity enhancements for IoT NTN              Huawei, HiSilicon

R1-2405928         Discussion on IoT-NTN uplink capacity/throughput enhancement              Spreadtrum Communications

R1-2406006         Discussion on the IoT -NTN uplink capacity/throughput enhancements      CMCC

R1-2406077         Discussion on the IoT-NTN uplink capacity/throughput enhancements      TCL

R1-2406111         IoT-NTN uplink capacity/throughput enhancement    InterDigital, Inc.

R1-2406133         Discussion on UL capacity enhancement for IoT NTN              ZTE Corporation, Sanechips

R1-2406205         Discussion on IoT-NTN uplink capacity enhancement              vivo

R1-2406232         Discussion on IoT-NTN uplink capacity/throughput enhancement              OPPO

R1-2406278         Discussion on IoT-NTN uplink capacity enhancement              Xiaomi

R1-2406362         Discussion on UL capacity enhancement for IoT NTN              CATT

R1-2406427         IoT-NTN uplink capacity enhancement         Nokia, Nokia Shanghai Bell

R1-2406449         Discussion on IoT-NTN uplink capacity/throughput enhancement              LG Electronics

R1-2406512         Discussion on uplink capacity enhancement for IoT NTN              Lenovo

R1-2406556         IoT-NTN uplink capacity/throughput enhancement    NEC

R1-2406573         IoT NTN OCC methods for NPUSCH and NPRACH  Sharp

R1-2406673         Discussion on uplink capacity/throughput enhancement for IoT-NTN      Samsung

R1-2406741         Discussion on uplink capacity/throughput enhancement for IoT NTN      ETRI

R1-2406780         IoT-NTN - uplink capacity/throughput enhancement  MediaTek Inc.

R1-2406809         On uplink capacity enhancements for IoT-NTN           Ericsson

R1-2406866         On IoT-NTN Uplink Capacity Enhancement Apple

R1-2407052         IOT-NTN uplink capacity/throughput enhancement   Qualcomm Incorporated

R1-2407138         Views on UL Capacity Enh for IoT-NTN      Inmarsat, Viasat              Late submission

R1-2407296         FL Summary #1 for IoT-NTN       Moderator (Sony)

From Wednesday session

Agreement

RAN1 studies whether the following types of UL transmission gap will impact the design of OCC for IoT-NTN when considering e.g. phase continuity

·       UL gaps for synchronization (from Rel-13)

·       Gaps around NPRACH occasions

·       UL timing adjustment gaps and segmentation for IoT-NTN (from Rel-17)

·       TDM DMRS that are muted

·       Guard periods for 3.75kHz UL transmissions

R1-2407297         FL Summary #2 for IoT-NTN       Moderator (Sony)

From Friday session

Agreement

The following combinations are considered for further simulation in RAN1 for 3.75kHz SCS OCC for NPUSCH format 1:

·       Option 1: OCC2, Symbol-level, TDM DMRS

·       Option 2: OCC2, Symbol-level, CDM DMRS with new pattern

·       Option 3: OCC2, Slot-level, TDM DMRS

·       Option 4: OCC2, Slot-level, CDM DMRS with legacy pattern

·       Option 6: OCC4, Symbol-level, CDM DMRS with new pattern

The following combinations are considered for further simulation in RAN1 for 15kHz SCS OCC for NPUSCH format 1:

·       Option 1: OCC2, Symbol-level, TDM DMRS

·       Option 3: OCC2, Slot-level, TDM DMRS

·       Option 4: OCC2, Slot-level, CDM DMRS with legacy pattern

·       Option 5: OCC4, Symbol-level, TDM DMRS

·       Option 7: OCC4, Slot -level, TDM DMRS

·       Option 8: OCC4, Slot-level, CDM DMRS with legacy pattern

Note 1: For TDM, the legacy DMRS pattern, with DMRS symbols appropriately muted/blanked is used. Companies to report their assumption on whether spreading is applied to the legacy DMRS pattern for 15 kHz SCS.

Note 2: Companies to report DMRS sequence applied.

Agreement

For 3.75kHz SCS, NPUSCH format 1 simulations are performed using an appropriate MCS with SNR at least in the range of -8dB to 0dB.

Final summary in R1-2407563.

 RAN1#118-bis

9.11   Non-Terrestrial Networks (NTN) for NR Phase 3, Internet of Things (IoT) Phase 3, and IoT-NTN TDD mode

Please refer to RP-241789 for detailed scope of the WI for NR-NTN Phase 3. Please refer to RP-241624 for detailed scope of the WI for IoT-NTN Phase 3. Please refer to RP-242415 for detailed scope of the WI for Introduction of IoT-NTN TDD mode.

R1-2409226         Session notes for 9.11 (Non-Terrestrial Networks for NR Phase 3 and Internet of Things Phase 3)    Ad-Hoc Chair (Huawei)

Friday decision: The session notes are endorsed and contents reflected below.

[118bis-R19-NTN] – Mohamed (Thales

Email discussion on Rel-19 NTN enhancement)

-        To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2407771         Work plan for Rel-19 NR_NTN_Ph3             THALES, CATT

R1-2409255         IRIS² - The New EU Programme Providing Secure Communications Via Satellites       ESA

From AI 5

R1-2407590         LS on common TA in a regenerative payload scenario              RAN2, CMCC

Decision: RAN1 response to be handled/moderated in agenda item 9.11 by Yi (CMCC).

R1-2409256         Moderator’s summary on the discussion of common TA in a regenerative payload scenario      Moderator (CMCC)

From Thursday session

Agreement

Response to RAN2 LS: A majority of companies in RAN1 thinks that it would not be a problem, depending on gNB implementation in a regenerative payload scenario, to stick to 0 as minimum possible value for TA common without introducing the negative value for ta-Common.

Comeback for draft LS - Yi

R1-2409257         Draft Reply LS on common TA values in the regenerative payload scenario              CMCC

Friday decision: The draft response LS to RAN2 is endorsed in R1-2409257, also cc to RAN4. Final LS is approved in R1-2409258       .

9.11.1    NR-NTN downlink coverage enhancement

R1-2407660         Discussion on downlink coverage enhancements for NR NTN              Huawei, HiSilicon

R1-2407721         Discussion on NR-NTN downlink coverage enhancement              Spreadtrum Communications

R1-2407743         Discussion on downlink coverage enhancements for NR NTN              China Telecom

R1-2407765         Discussions on downlink coverage enhancement for NR NTN              Fraunhofer IIS, Fraunhofer HHI

R1-2407766         NR NTN Downlink coverage enhancements THALES

R1-2407816         Discussion on DL coverage enhancements for NR-NTN              NICT

R1-2407878         Discussion on NR-NTN downlink coverage enhancement              vivo

R1-2407920         Discussion on NR-NTN DL coverage enhancement    CMCC

R1-2407933         Discussion on DL coverage enhancement for NR NTN              ZTE Corporation, Sanechips

R1-2407956         Discussion on NR-NTN downlink coverage enhancement              Xiaomi

R1-2408033         Further consideration on downlink coverage enhancement for NR NTN      CATT

R1-2408135         Discussion on NR-NTN downlink coverage enhancement              OPPO

R1-2408227         NR-NTN downlink coverage enhancement   NEC

R1-2408237         Discussion on NR-NTN downlink coverage enhancement              HONOR

R1-2408257         Discussion on NR-NTN downlink coverage enhancement              TCL

R1-2408298         Discussion on NR-NTN downlink coverage enhancement        LG Electronics

R1-2408310         NR-NTN downlink coverage enhancement   Baicells

R1-2408323         Discussion on downlink coverage enhancement for NR NTN              Lenovo

R1-2408361         NR-NTN Downlink Coverage Enhancement Panasonic

R1-2408426         On NR-NTN downlink coverage enhancement           Ericsson

R1-2408487         Discussion on NR-NTN Downlink Coverage Enhancement              Apple

R1-2408506         Discussion on downlink coverage enhancements        Fujitsu

R1-2408528         NR-NTN downlink coverage enhancement with beam groups              Sharp

R1-2408552         NR-NTN downlink coverage enhancement   InterDigital, Inc.

R1-2408578         Discussion on NR-NTN downlink coverage enhancement              ETRI

R1-2408663         Discussion on downlink coverage enhancement for NR-NTN              Samsung

R1-2408684         Discussion on downlink coverage enhancements for NR NTN              CCU

R1-2408716         NR-NTN downlink coverage enhancement   MediaTek Inc.

R1-2408727         Further discussion on downlink coverage enhancements for NR over NTN             Nokia, Nokia Shanghai Bell

R1-2409037         Discussion on DL coverage enhancement for NR-NTN              NTT DOCOMO, INC.       (rev of R1-2408802)

R1-2408824         Discussion on NR-NTN DL coverage enhancement    KT Corp.

R1-2408867         Downlink coverage enhancement for NR NTN            Qualcomm Incorporated

R1-2408880         Downlink Coverage Enhancement for NR NTN          Google Ireland Limited

R1-2408894         Discussion on downlink coverage enhancement for NR-NTN              CSCN

R1-2408937         Downlink Coverage Enhancements for NR NTN        CEWiT

R1-2409004         Operator views on DL Coverage Enhancements for NR NTN              Inmarsat, Viasat  (rev of R1-2408945)

R1-2408949         Discussion on NTN System Level Downlink Coverage Enhancement       EchoStar, Eutelsat Group, Thales, Terrestar

(moved from agenda item 5)

Follow up discussions from RAN1#118 on RAN2 LS for DL coverage enhancements (Rel-19 NR-NTN)

R1-2407831         Draft reply LS on DL coverage enhancements            vivo

R1-2408440         Discussion on RAN2 LS on DL Coverage Enhancements              Apple

R1-2408441         Draft Reply LS to RAN2 on DL Coverage Enhancements              Apple

From Friday session

R1-2409288         Draft Reply LS on DL coverage enhancements       Moderator (THALES)

Conclusion: No response at RAN1#118bis.

R1-2407767         FL Summary #1: NR-NTN downlink coverage enhancements              THALES

From Monday session

Agreement

For NR NTN, support extended periodicity of the half frames with SS/PBCH blocks assumed by UE during initial access.

·       The maximum of the additional default value (apart from the existing 20ms value) is at least 160ms.

o   FFS: whether 320ms can be supported as the maximum of the additional default value instead of or in addition to 160ms.

R1-2407768         FL Summary #2: NR-NTN downlink coverage enhancements              THALES

From Wednesday session

Agreement

Support PDCCH CSS Link level enhancement in Rel-19 for all CSS types except type 3.

• The following techniques are for further study:
• PDCCH repetition, including:
• Option 1: Intra-slot PDCCH repetition
• Option 2: Inter-slot PDCCH repetition
• CORESET length (i.e. number of OFDM symbols) extension
• DCI format optimization (e.g. size reduction, etc)
• Note: the same technique is intended to apply to all search space types targeted for link level enhancements
• For the above techniques, at least the following aspects should be discussed for the relevant candidate techniques:
• Configuration
• Backward compatibility and UE behaviour of legacy UE
• Linked Search Space
• Blocking probability
• DCI format size budget
• Resource overhead
• Impact on CORESET0
• Focus on coverage enhancement for set 1-3 with a target CNR of -8 dB for NR NTN DL coverage enhancements at link level.
• FFS: whether to apply the selected solution to PDCCH CSS type3 and PDCCH USS

R1-2407769         FL Summary #3: NR-NTN downlink coverage enhancements              THALES

From Friday session

Agreement

For PDSCH with Msg4 Link level enhancement:

• Continue studying PDSCH repetition
• Further discuss the specification impact for at least the following:
• Procedure and signaling
• Repetition factor
• Focus on coverage enhancement for set 1-3 with a target CNR of -8 dB for NR NTN DL coverage enhancements at link level.

Final summary in R1-2407770.

9.11.2    Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands

R1-2407661         Discussion on HD-FDD RedCap UEs and eRedCap UEs for FR1-NTN      Huawei, HiSilicon

R1-2407722         Discussion on support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands Spreadtrum Communications

R1-2407744         Discussion on Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands China Telecom

R1-2407879         Discussion on support of RedCap and eRedCap UEs with NR-NTN      vivo

R1-2407921         Discussion on the collision issues of HD-FDD Redcap UE in FR1-NTN             CMCC

R1-2407934         Discussion on support of RedCap/eRedCap UEs for NR NTN              ZTE Corporation, Sanechips

R1-2407957         Discussion on the support of Redcap and eRedcap UEs in NR NTN      Xiaomi

R1-2408034         Discussion on the enhancement of RedCap and eRedCap UEs In NTN      CATT

R1-2408136         Discussion on supporting of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands OPPO

R1-2408238         Discussion on support of RedCap and eRedCap UEs in NR NTN              HONOR

R1-2408258         Discussion on HD-FDD Redcap UEs and eRedcap UEs for FR1-NTN      TCL

R1-2408299         Discussion on support of (e)RedCap UEs with NR-NTN operating in FR1-NTN bands            LG Electronics

R1-2408488         Discussion on support of RedCap UEs with NR NTN operation              Apple

R1-2408553         Discussion on half-duplex RedCap issues for NTN FR1 operation              InterDigital, Inc.

R1-2408579         Discussion on HD UEs with NR NTN           ETRI

R1-2408664         Discussion on support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands Samsung

R1-2408717         Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands  MediaTek Inc.

R1-2408728         Additional considerations on (e)RedCap operation in NR over NTN      Nokia, Nokia Shanghai Bell

R1-2408734         On HD-FDD Redcap UEs for NTN Ericsson

R1-2408803         Discussion on support of RedCap and eRedCap UEs in FR1-NTN              NTT DOCOMO, INC.

R1-2408811         Discussion on support of RedCap/eRedCap UEs in NTN              CAICT

R1-2408868         Support of Redcap and eRedcap UEs in NR NTN       Qualcomm Incorporated

R1-2409101         Summary #1 for Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands      Moderator (CATT)

Presented in Tuesday session.

R1-2409102         Summary #2 for Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands      Moderator (CATT)

From Wednesday session

Conclusion

The different use cases (e.g. the collision happening in different channel types or different scheduling cases) from RAN1#118 agreement for collision case 3 (Semi-statically configured DL reception collides with semi-statically configured UL transmission) consist of pairs of one semi-statically configured DL reception and one semi-statically configured UL transmission, among:

• Semi-statically configured DL reception includes Type-0/0A/0B/1/2-PDCCH CSS and dedicated semi-statically configured PDCCH USS/PDSCH SPS/CSI-RS/PRS/[Type 3 PDCCH CSS]
• Semi-statically configured UL transmission includes semi-statically configured PUSCH/PUCCH/SRS

R1-2409103         Summary #3 for Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands      Moderator (CATT)

Presented in Friday session.

Final summary in R1-2409295.

9.11.3    NR-NTN uplink capacity/throughput enhancement

R1-2409092         Discussion on uplink capacity/throughput enhancement for FR1-NTN      Huawei, HiSilicon             (rev of R1-2407662)

R1-2407723         Discussion on NR-NTN uplink capacity/throughput enhancement              Spreadtrum Communications, SGITG

R1-2407745         Discussion on NR-NTN uplink enhancement              China Telecom

R1-2407817         Discussion on NR-NTN uplink capacity/throughput enhancement              NICT

R1-2407880         Discussion on NR-NTN uplink capacity enhancement              vivo

R1-2407922         Discussion on the NR-NTN uplink capacity/throughput enhancements      CMCC

R1-2407935         Discussion on UL capacity enhancement for NR NTN              ZTE Corporation, Sanechips

R1-2407958         Discussion on NR-NTN PUSCH capacity enhancement              Xiaomi

R1-2408035         Discussion on UL capacity enhancement for NR NTN              CATT

R1-2408137         Discussion on NR-NTN uplink capacity/throughput enhancement              OPPO

R1-2408228         NR-NTN uplink capacity/throughput enhancement    NEC

R1-2408239         Discussion on NR-NTN UL capacity/throughput enhancement              HONOR

R1-2408242         Discussion on the NR-NTN uplink capacity/throughput enhancements      TCL

R1-2408300         Discussion on NR-NTN uplink capacity/throughput enhancement              LG Electronics

R1-2408330         NR-NTN uplink capacity enhancement         Sharp

R1-2408489         Discussion on NR-NTN Uplink Capacity Enhancement              Apple

R1-2408505         Discussion on uplink capacity/cell throughput enhancement for FR1-NTN             Fujitsu

R1-2408540         Uplink capacity/throughput enhancement for NR-NTN              Panasonic

R1-2408543         Discussion on the NR-NTN uplink capacity/throughput enhancements      Lenovo

R1-2408554         NR-NTN uplink capacity/throughput enhancement    InterDigital, Inc.

R1-2408580         Discussion on NR-NTN uplink capacity/throughput enhancement              ETRI

R1-2408665         Discussion on uplink capacity/throughput enhancement for NR-NTN      Samsung

R1-2408686         On uplink capacity/cell throughput enhancement for NR NTN              Ericsson

R1-2408718         NR-NTN uplink capacity and throughput enhancements              MediaTek Inc.

R1-2408729         Further discussion on uplink capacity enhancements for NR over NTN      Nokia, Nokia Shanghai Bell

R1-2408804         Discussion on NR-NTN uplink capacity/throughput enhancement              NTT DOCOMO, INC.

R1-2408869         NR-NTN uplink capacity / throughput enhancement   Qualcomm Incorporated

R1-2408946         Operator views on UL Capacity Enhancements for NR NTN              Inmarsat, Viasat  (Late submission)

R1-2408965         Views on NR-NTN PUSCH capacity enhancement    Mitsubishi Electric RCE

R1-2409018         Feature lead summary #1 of AI 9.11.3 on NR-NTN uplink capacity and throughput enhancements    Moderator (MediaTek)

Presented in Tuesday session.

R1-2409019         Feature lead summary #2 of AI 9.11.3 on NR-NTN uplink capacity and throughput enhancements    Moderator (MediaTek)

From Thursday session

Working assumption

For the normative phase,

• Support OCC length 2 with inter-slot OCC to multiplex up to 2 UEs.
• Support OCC length 4 with one of the following OCC techniques
• Option 1: Inter-slot with OCC length 4 to multiplex up to 4 UEs.
• Option 2: Intra-symbol pre-DFT OCC with OCC length 4 to multiplex up to 4 UEs.
• Option 3: Combination of Inter-slot OCC with OCC length 2 and intra-symbol pre-DFT OCC with OCC length 2 to multiplex up to 4 UEs.
• Note 1:
• At least consider 8 slots, 16 slots, and 20 slots for VoIP with BLER 2% target, with 1 RB, 2 RBs when comparing Option 1, Option 2, and Option 3. Companies can additionally report on 4 slots at least for 2 RBs.
• Option 2 assumes TBoMS, FFS Option 3 assumes TBoMS

Note 2: as part of the working assumption, it is assumed that there would be separate UE capabilities for OCC length 2 and OCC length 4, where UE capability for OCC length 2 is a prerequisite for UE capability for OCC length 4.

Conclusion

For TBS calculation and rate matching for OCC with PUSCH, for inter-slot OCC in the working assumption of RAN1#118bis:

• for inter-slot OCC for OCC length 2 and for inter-slot OCC for OCC length 4 in option 1 in the working assumption of RAN1#118bis
• No change in determination of TBS.
• No change for rate matching.

Agreement

For RV cycling for OCC with PUSCH

• For inter-slot OCC for OCC length 2 and for inter-slot OCC for OCC length 4 in option 1 in the working assumption of RAN1#118bis
• Same RV value is used in one OCC group (i.e., OCC length applied to N slots).
• FFS: RV cycling can be additionally used across OCC groups.

R1-2409020         Feature lead summary #3 of AI 9.11.3 on NR-NTN uplink capacity and throughput enhancements    Moderator (MediaTek)

From Friday session

Agreement

For OCC sequence for OCC with PUSCH:

• For OCC length 2, re-use orthogonal sequence [1 1; 1 -1]

9.11.4    IoT-NTN uplink capacity/throughput enhancement

R1-2407663         Discussion on UL capacity enhancements for IoT NTN              Huawei, HiSilicon

R1-2407724         Discussion on IoT-NTN uplink capacity/throughput enhancement              Spreadtrum Communications

R1-2407881         Discussion on IoT-NTN uplink capacity enhancement              vivo

R1-2407923         Discussion on the IoT -NTN uplink capacity/throughput enhancements      CMCC

R1-2407936         Discussion on UL capacity enhancement for IoT NTN              ZTE Corporation, Sanechips

R1-2407959         Discussion on IoT-NTN uplink capacity enhancement              Xiaomi

R1-2408036         Discussion on UL capacity enhancement for IoT NTN              CATT

R1-2408138         Discussion on IoT-NTN uplink capacity/throughput enhancement              OPPO

R1-2408229         IoT-NTN uplink capacity/throughput enhancement    NEC

R1-2408243         Discussion on the IoT-NTN uplink capacity/throughput enhancements      TCL

R1-2408301         Discussion on IoT-NTN uplink capacity/throughput enhancement              LG Electronics

R1-2408324         Discussion on uplink capacity enhancement for IoT NTN              Lenovo

R1-2408346         IoT-NTN uplink capacity enhancement         Nokia, Nokia Shanghai Bell

R1-2408425         On IoT-NTN uplink capacity enhancements Sony

R1-2408490         Discussion on IoT-NTN Uplink Capacity Enhancement              Apple

R1-2408529         IoT NTN OCC methods for NPUSCH and NPRACH  Sharp

R1-2408555         IoT-NTN uplink capacity/throughput enhancement    InterDigital, Inc.

R1-2408581         Discussion on uplink capacity/throughput enhancement for IoT NTN      ETRI

R1-2408666         Discussion on uplink capacity/throughput enhancement for IoT-NTN      Samsung

R1-2408719         IoT-NTN uplink capacity and throughput enhancement              MediaTek Inc.

R1-2408735         On uplink capacity enhancements for IoT-NTN           Ericsson

R1-2408870         IOT-NTN uplink capacity/throughput enhancement   Qualcomm Incorporated

R1-2408877         IoT-NTN uplink capacity/throughput enhancement    Nordic Semiconductor ASA

R1-2409192         FL Summary #1 for IoT-NTN       Moderator (Sony)

From Tuesday session

Agreement

At least the following schemes are supported for single-tone:

• For 3.75kHz SCS OCC for NPUSCH format 1:
• OCC length 2, Symbol-level
• FFS: DMRS pattern(s)
• For 15kHz SCS OCC for NPUSCH format 1:
• OCC length 2, Slot-level, CDM DMRS with legacy pattern
• FFS: CDM details, e.g. with or without spreading

R1-2409193         FL Summary #2 for IoT-NTN       Moderator (Sony)

From Thursday session

Agreement

For NPRACH transmission, inter-symbol group OCC is not further studied.

Agreement

For support of single-tone OCC for NPUSCH format 1, RAN1 studies:

• The parameters that need to be signalled, considering the following:
• OCC codeword
• Enabling of OCC feature
• FFS: other parameters
• For dynamic grant in RRC CONNECTED, study which and whether any parameters are signalled via DCI and which and whether any parameters are signalled by RRC.
• FFS: whether/how to support cases other than dynamic grant in RRC CONNECTED, e.g. Msg3, PUR, CB Msg3 EDT.

Final summary in R1-2409309.

9.11.55    IoT-NTN TDD mode

Prioritize discussion on study phase objective in RAN1#118bis.

R1-2408273         WP for Introduction of IoT-NTN TDD mode WI        Iridium Satellite LLC

R1-2407689         Discussion on IoT-NTN TDD mode              Huawei, HiSilicon

R1-2407725         Discussion on IoT-NTN TDD mode              Spreadtrum Communications

R1-2407924         Discussion on the new NB-IoT NTN TDD mode        CMCC

R1-2407937         Discussion on the IoT-NTN TDD mode        ZTE Corporation, Sanechips

R1-2407960         Discussion on IoT-NTN TDD mode              Xiaomi

R1-2408037         Considerations on IoT-NTN TDD mode       CATT

R1-2408139         Discussion on IoT-NTN TDD mode              OPPO

R1-2408302         Discussion on IoT-NTN TDD mode              LG Electronics

R1-2408347         Discussion on IoT-NTN TDD mode              Nokia, Nokia Shanghai Bell

R1-2408491         Discussion on IoT-NTN TDD mode              Apple

R1-2408667         Discussion on IoT-NTN TDD mode              Samsung

R1-2408874         Discussion on introduction of IoT-NTN TDD mode   SageRAN              (rev of R1-2408078)

R1-2408919         On R19 TDD IoT-NTN     Nordic Semiconductor ASA

R1-2408400         Analysis - loT-NTN TDD mode DL sync    Iridium Satellite LLC

Decision: The document is noted.

R1-2408871         IOT-NTN TDD mode      Qualcomm Incorporated

Decision: The document is noted.

R1-2407772         Discussion on IoT-NTN TDD mode            THALES

Decision: The document is noted.

R1-2408736         On TDD mode for IoT-NTN          Ericsson

Decision: The document is noted.

R1-2407882         Discussion on IoT-NTN TDD mode            vivo

Decision: The document is noted.

R1-2409038         Feature lead summary#1 on IoT-NTN TDD mode  Moderator (Qualcomm Incorporated)

Presented in Monday session.

R1-2409039         Feature lead summary#2 on IoT-NTN TDD mode  Moderator (Qualcomm Incorporated)

From Thursday session

Agreement

The target operating DL CNR of NB-IoT NTN TDD is obtained following the parameters in TR 36.763 and modifying the carrier frequency to 1.6GHz:

• For LEO-600, the operating DL CNR is 4.91dB (i.e. with 0dBi UE antenna gain).
• For LEO-1200, the operating DL CNR is 5.51dB (i.e. with 0dBi UE antenna gain).
• When reporting link level simulation results, companies are encouraged to report the CNR margin with respect to the above operating DL CNRs.
• Companies may report values for other scenarios (e.g. UE antenna gain of -5.5 dBi, LEO-800) with the corresponding assumptions.

Agreement

For the study phase, RAN1 assumes as a baseline for evaluations (which includes DL synchronization as per the WID) that downlink PHY channels and signals are transmitted on the anchor carrier following subframe index/location and SFN mapping of NB-IoT NTN FDD.

• For the purpose of study, the DL subframes of the Rel-19 TDD pattern may not fully cover all the instances of the PHY channels and signals and eNB will not transmit the corresponding instances.
• FFS: What is the TDD pattern

Agreement

RAN1 evaluates via link level simulations the following:

• NPSS/NSSS detection
• NPBCH decoding

Agreement

The impact of the TDD pattern at least on the following channels / signals are evaluated at least qualitatively (e.g. specification impact, number of available instances, etc.):

• SIB1-NB
• Other SIBs needed for basic NB-IoT NTN operation (e.g. SIB2, SIB31)
• Paging
• NPRACH / RAR
• NPSS/NSSS/NPBCH
• NPDCCH, NPUSCH, NPDSCH
• Note: Study for the above channels / signals may continue during the normative phase.
• It is up to companies to perform link level evaluations for some of the aspects above.

Agreement

For link level simulations of NPSS / NSSS / NPBCH, RAN1 uses the following assumptions:

Agreement

For the study phase, RAN1 evaluates the following combination of N (in radio frames) and D (D = number of consecutive downlink subframes):

• N = 9:
• D = 8
• D = 20
• D = 30
• N = 8:
• D = 20
• Companies to report which subframe indices are included in the set of consecutive downlink subframes.
• Other combinations are not precluded to be reported by companies

NOTE: This does not imply that the above combinations are the only ones to be considered during the normative phase.

Agreement

For the study phase, RAN1 evaluates the following combination of N (in radio frames) and U (U = number of consecutive uplink subframes):

• N = 9:
• U = 8
• U = 20
• U = 30
• N = 8:
• U = 20
• Companies to report which subframe indices are included in the set of consecutive uplink subframes.
• Other combinations are not precluded to be reported by companies
• For evaluations including both uplink and downlink (if any), companies are encouraged to prioritize the case of D=U

NOTE: This does not imply that the above combinations are the only ones to be considered during the normative phase.

Agreement

For the study phase, RAN1 assumes as a baseline for evaluations that uplink PHY channels are transmitted on the anchor carrier following subframe index/location and SFN mapping of NB-IoT NTN FDD.

• For the purpose of study, the UL subframes of the Rel-19 TDD pattern may not fully cover all the instances of the PHY channels and eNB will not receive the corresponding instances.
• FFS: What is the TDD pattern

 RAN1#119

9.11   Non-Terrestrial Networks (NTN) for NR Phase 3, Internet of Things (IoT) Phase 3, and IoT-NTN TDD mode

Please refer to RP-241789 for detailed scope of the WI for NR-NTN Phase 3. Please refer to RP-242397 for detailed scope of the WI for IoT-NTN Phase 3. Please refer to RP-242415 for detailed scope of the WI for Introduction of IoT-NTN TDD mode.

R1-2410848         Session notes for 9.11 (Non-Terrestrial Networks for NR Phase 3 and Internet of Things Phase 3)    Ad-Hoc Chair (Huawei)

Friday decision: The session notes are endorsed and contents reflected below.

[119-R19-NTN] – Mohamed (Thales)

Email discussion on Rel-19 NTN enhancement

-        To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2409439         Work plan for Rel-19 NR_NTN_Ph3             THALES, CATT              Late submission

R1-2409564         Work plan for WID: introduction of IoT-NTN TDD mode              Iridium Satellite LLC

From AI 5

R1-2409343         LS on OCC for CB-msg3 NPUSCH            RAN2, vivo

Decision: Response is needed – Martin (Sony).

From Wednesday session

Agreement

The following response is sent in reply to RAN2 LS R1-2409343:

Response to RAN2: The OCC solution that RAN1 is working on may be applied to CB-Msg3 NPUSCH format 1 single tone at least for OCC length 2, for the subcarrier spacing(s) for which CB-Msg3 is supported, when the power imbalance is small. The design details for the OCC solution are ongoing.

Action to RAN2: RAN1 respectfully asks RAN2 to take the above information into account.

Comeback for draft LS (Martin)

From Thursday session

R1-2410894         Draft Reply LS on OCC for CB-msg3 NPUSCH     Moderator (Sony)

Agreement

The draft LS reply to RAN2 is endorsed in R1-2410894. Final LS is approved in R1-2410895.

9.11.1    NR-NTN downlink coverage enhancement

R1-2409405         Discussion on downlink coverage enhancements for NR NTN              Huawei, HiSilicon

R1-2409434         NR NTN Downlink coverage enhancements THALES

R1-2409451         Discussions on downlink coverage enhancement for NR NTN              Fraunhofer IIS, Fraunhofer HHI

R1-2409473         Discussion on NTN System Level Downlink Coverage Enhancement       EchoStar

R1-2409527         Discussion on NR-NTN DL coverage enhancement    CMCC

R1-2409614         Discussion on downlink coverage enhancement for NR-NTN              Samsung

R1-2409650         Discussion on NR-NTN downlink coverage enhancement              Spreadtrum, UNISOC

R1-2409698         Discussion on NR-NTN downlink coverage enhancement              vivo

R1-2409719         NR-NTN downlink coverage enhancement   InterDigital, Inc.

R1-2409726         Discussion on DL coverage enhancement for NR NTN              ZTE Corporation, Sanechips

R1-2409823         On NR-NTN Downlink Coverage Enhancement         Apple

R1-2409831         Discussion on NR-NTN downlink coverage enhancement        LG Electronics

R1-2409870         NR-NTN downlink coverage enhancement   NEC

R1-2409883         Discussion on NR-NTN downlink coverage enhancement              Xiaomi

R1-2409958         Discussion on DL coverage enhancements for NR-NTN              NICT

R1-2409978         Further consideration on downlink coverage enhancement for NR NTN      CATT

R1-2410064         Discussion on NR-NTN downlink coverage enhancement              TCL

R1-2410079         Discussion on NR-NTN downlink coverage enhancement              OPPO

R1-2410129         Discussion on downlink coverage enhancements        Fujitsu

R1-2410160         NR-NTN downlink coverage enhancement techniques              Sharp

R1-2410169         On NR-NTN downlink coverage enhancement           Ericsson

R1-2410182         Discussion on NR-NTN downlink coverage enhancement              HONOR

R1-2410277         Discussion on NR-NTN downlink coverage enhancement              ETRI

R1-2410282         NR-NTN Downlink Coverage Enhancement Panasonic

R1-2410364         Discussion on downlink coverage enhancement for NR NTN              Lenovo

R1-2410405         Discussion on DL coverage enhancement for NR-NTN              NTT DOCOMO, INC.

R1-2410415         Discussion on downlink coverage enhancement for NR NTN              Baicells

R1-2410495         Downlink coverage enhancement for NR NTN            Qualcomm Incorporated

R1-2410526         NR-NTN downlink coverage enhancement   MediaTek Inc.

R1-2410546         Downlink Coverage Enhancement for NR NTN          Google Ireland Limited

R1-2410553         Further discussion on downlink coverage enhancements for NR over NTN             Nokia, Nokia Shanghai Bell

R1-2410567         Discussion on NR-NTN DL coverage enhancement    KT Corp.

R1-2410584         Discussion on Downlink Coverage Enhancements for NR NTN              CEWiT

R1-2410619         Operator views on DL Coverage Enhancements for NR NTN              Inmarsat, Viasat

R1-2409435         FL Summary #1: NR-NTN downlink coverage enhancements              THALES

From Tuesday session

Agreement

For PDSCH with Msg4 Link level enhancement:

• Support PDSCH repetition
• FFS: signalling design including number of repetitions
• FFS: impact on UE capability
• Note: the target coverage enhancement to bridge the gap with respect to single Msg4 transmission is 2.8 dB
• Focus on coverage enhancement for set 1-3 with a target CNR of -8 dB for NR NTN DL coverage enhancements at link level.